WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Dom0 crash when DomU maxmem specified

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Dom0 crash when DomU maxmem specified
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 4 Jul 2009 20:22:31 +1000
Delivery-date: Sat, 04 Jul 2009 03:23:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn8kVbO2ZkyJX3KS3y5xoWZolAy9Q==
Thread-topic: Dom0 crash when DomU maxmem specified
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

James

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

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