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 hang when "xm mem-set 0 16"

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] dom0 hang when "xm mem-set 0 16"
From: "Zheng, Jeff" <jeff.zheng@xxxxxxxxx>
Date: Tue, 30 May 2006 16:20:31 +0800
Delivery-date: Tue, 30 May 2006 01:21:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaDweob7Koi2kIeQbStamDVvbksaQ==
Thread-topic: dom0 hang when "xm mem-set 0 16"
I input "xm mem-set 0 16" and then dom0 hang. The serial output is:
###############################################
(XEN) microcode: No new microcode data for CPU1
(XEN) microcode: No new microcode data for CPU2
IA-32 Microcode Update Driver v1.14-xen unregistered
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
Kernel panic - not syncing: Out of memory and no killable processes...
###############################################

It's possible that administrator wants to "xm mem-set 0 160" but
actually input "xm mem-set 0 16", and then dom0 hangs. Any method to
avoid it?

Bests
Jeff

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

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