From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Bug: Limitation of <=2GB RAM in domU persists with 4.3.0 Date: Wed, 24 Jul 2013 12:31:02 -0400 Message-ID: <20130724163102.GA6308@phenom.dumpdata.com> References: <51EF04D8.1090600@bobich.net> <20130724140813.GH2518@phenom.dumpdata.com> <2aa84a31b7b17c2ea6d8483a281ad3f5@mail.shatteredsilicon.net> <20130724160639.GB5804@phenom.dumpdata.com> <8426aecf79e7f55c21bbe259014591a2@mail.shatteredsilicon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <8426aecf79e7f55c21bbe259014591a2@mail.shatteredsilicon.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Gordan Bobic Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Wed, Jul 24, 2013 at 05:14:32PM +0100, Gordan Bobic wrote: > On Wed, 24 Jul 2013 12:06:39 -0400, Konrad Rzeszutek Wilk > wrote: > > >>>Are you also able to get the serial log from the guest? (IF this is > >>>Linux?) I usually have this in my guest config: > >>> > >>>serial='pty' > >>> > >>>and when Linux boots up I add 'console=ttyS0,115200 loglevel=8 > >>debug' > >>>which will output everything to the 'xl console | tee > >>>/tmp/log'. > >> > >>The intended guest is XP64. I will, however, get a Linux guest up > > > >Ah, I am not actually sure how Linux will work. I hadn't had a chance > >to test that recently :-( > > As long as it brings up the serial console, that should be > sufficient, but working VNC to text console login would be > convenient. The main thing I want to find on it is the > BAR mapping addresses from lspci and compare that to the > e820 map from dmesg. I see. That should work for you. > > I wouldn't expect the memory map provided by SeaBIOS and > the BAR mappings configured by qemu-dm to differ > depending on the domU OS. Or am I wrong here? They might. The patches to fix the 2GB limit went in qemu-xen-traditional meaning you have to use: device_model_version = 'qemu-xen-traditional' in your guest config (which I think you are already doing). I don't recall what the situation is with upstream SeaBIOS. > > If there is any overlap, the problem should be obvious. > If there is no overlap, then something even more > bizzare is going on, but we can worry about that > later. :)