This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston

To: Ed Smith <esmith@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Problem booting fully virtualized (Intel VT) 32b gueston XEN32 unstable
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Fri, 28 Apr 2006 16:31:48 +0100
Cc: "Zhao, Yunfeng" <yunfeng.zhao@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 28 Apr 2006 08:32:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <44522D18.2060808@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <08B1877B2880CE42811294894F33AD5C024965@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <44522D18.2060808@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Apr 28, 2006 at 10:56:24AM -0400, Ed Smith wrote:

> That worked.  I set my dom0_mem=256M and my domUs now boot fine.
> Is this currently a restriction in 32bit XEN?  I don't have to adjust
> the dom0 memory on 64bit XEN.  I thought the balloon driver was supposed
> to allow dom0 to allocate up all the available memory for the hypervisor
> and then let the hypervisor give it out to domU's as needed.

That all works for paravirt domains.  For VT domains, there's certainly one
outstanding bug with not enough memory being ballooned out, because it's not
taking proper account of the video memory required for the domain -- perhaps
you could look into that?  I'm suprised by the double-fault though -- that's
obviously a more serious bug than merely failing to balloon.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>