Re: [Xen-devel] Dom0 crash when DomU maxmem specified

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

It looks like suddenly the machine won't talk to me anymore :)

Not much use sorry. I'm at home (flu) and the machine is at work. What sort of 
info do you need?

James

-----Original Message-----
From: "Keir Fraser"<keir.fraser@xxxxxxxxxxxxx>
Sent: 4/07/09 8:59:37 PM
To: "James Harper"<james.harper@xxxxxxxxxxxxxxxx>, 
"xen-devel@xxxxxxxxxxxxxxxxxxx"<xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Dom0 crash when DomU maxmem specified

On 04/07/2009 11:22, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> I have a windows DomU with memory=768 and maxmem=5120, I just noticed
> that since upgrading to 3.4.1-rc5 that Windows thinks it has 5G of
> memory, while 'xm list' says it only has 768M and 'xm info' roughly
> matches (eg 8G physical memory, 5G remaining, 3G used by various
> DomU's).
> 
> I then ran a few things in my DomU to see what would happen when it
> tried to use more than 768M of memory and unexpectedly, the entire Dom0
> crashed.
> 
> This worked as expected under 3.3.x

It probably has something to do with the populate-on-demand memory support
for HVM guests that was introduced in Xen 3.4. What does the dom0 crash look
like?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel