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-users

[Xen-users] HVM DomU with Kernel 2.6.27-19 on CentOS 5 hangs with 100% C

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] HVM DomU with Kernel 2.6.27-19 on CentOS 5 hangs with 100% CPU at Linux bootup on Xen 3.2.1
From: Martin Troester <TroyMcClure@xxxxxx>
Date: Tue, 13 Apr 2010 22:53:29 +0200
Delivery-date: Tue, 13 Apr 2010 13:55:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (X11/20100317)
Dear Xen Community,

today we tried to upgrade our base server from a Xeon E5430 to a Xeon X5570 (Nehalem). This worked fine so far, but our DomUs with Kernel 2.6.27 no longer boot - they start up until the following message appears:

[..]
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer

Afterwards, the CPU utilization in xm top/xm list shows one VCPU assigned to that VM, even if more have been specified in the config file. This VCPU is 100% busy - so it appears to be caught in some kind of a loop?

As only one VCPU is shown at this point, it appears to be early during bootup, not all VCPUs have been detected and assigned to that VM.

As the very same image runs without problems with the same Dom0 and DomU config on the "old" Xeon, and other DomUs still run on the new setup, this seems to be related to this kernel version.

Any help to debug deeper into this are highly appreciated.

Thanks!
Martin

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

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