Joern Bredereck
2009-Jun-30 10:35 UTC
[Xen-users] [Fwd: DomUs don''t shutdown with cpu-pinning configured]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, since pinning the cpu cores to Dom0 and the DomUs the shutdown of the VMs doesn''t work anymore. When shutting down or rebooting a DomU the DomU just freezes after the shutdown process but won''t reboot or stop the DomU. The shutdown itself seems to be complete though. We can reproduce this problem on 4 different servers. Some info about our setup: root@xen1:~# uname -a Linux xen1 2.6.24-24-xen #1 SMP Wed Apr 15 17:05:38 UTC 2009 x86_64 GNU/Linux root@xen1:~# dpkg -l |grep xen ii libxen3 3.3.0-1ubuntu7~hardy1 library interface for Xen, a Virtual Machine ii linux-image-2.6.24-24-xen 2.6.24-24.53 Linux kernel image for version 2.6.24 on Thi ii linux-restricted-modules-2.6.24-24-xen 2.6.24.17-24.1 Non-free Linux 2.6.24 modules on Xen ii linux-ubuntu-modules-2.6.24-24-xen 2.6.24-24.39 Ubuntu supplied Linux modules for version 2. ii python-xen-3.3 3.3.0-1ubuntu7~hardy1 python bindings for Xen, a Virtual Machine M ii xen-docs-3.3 3.3.0-1ubuntu7~hardy1 documentation for XEN, a Virtual Machine Mon ii xen-hypervisor-3.3 3.3.0-1ubuntu7~hardy1 The Xen Hypervisor for i386 and amd64. ii xen-utils-3.3 3.3.0-1ubuntu7~hardy1 XEN administrative tools root@xen1:~# grep cpu /etc/xen/* /etc/xen/repair:vcpus = ''1'' /etc/xen/repair:cpu = "2" /etc/xen/xend-config.sxp:# In SMP system, dom0 will use dom0-cpus # of CPUS /etc/xen/xend-config.sxp:# If dom0-cpus = 0, dom0 will take all cpus available /etc/xen/xend-config.sxp:(dom0-cpus 1) After shuttind down a DomU (in this case a Domain called "repair"): root@xen1:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1000 1 r----- 1312.2 repair 22 1024 1 ---s-- 15.5 root@xen1:~# xm vcpu-list Name ID VCPU CPU State Time(s) CPU Affinity Domain-0 0 0 5 r-- 1304.6 any cpu Domain-0 0 1 - --p 1.3 any cpu Domain-0 0 2 - --p 1.3 any cpu Domain-0 0 3 - --p 1.3 any cpu Domain-0 0 4 - --p 0.9 any cpu Domain-0 0 5 - --p 1.0 any cpu Domain-0 0 6 - --p 1.3 any cpu Domain-0 0 7 - --p 1.1 any cpu repair 22 0 2 --- 15.5 2 The only way to stop the Domain "repair" is to destroy it. The last 2 lines of the quemu-log is: shutdown requested in cpu_handle_ioreq Issued domain 22 poweroff The xend.log looks like this: [2009-06-30 00:27:01 5294] INFO (XendDomainInfo:1634) Domain has shutdown: name=repair id=22 reason=poweroff. [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:2389) XendDomainInfo.destroy: domid=22 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:2406) XendDomainInfo.destroyDomain(22) [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1939) Destroying device model [2009-06-30 00:27:01 5294] WARNING (image:472) domain repair: device model failure: no longer running; see /var/log/xen/qemu-dm-repair.log [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1946) Releasing devices [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing vif/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:888) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing vbd/768 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:888) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/768 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing vfb/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:888) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:1952) Removing console/0 [2009-06-30 00:27:01 5294] DEBUG (XendDomainInfo:888) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 Any idea how to fix this issue? Thanks in advance! Regards, Joern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpJ6lcACgkQeCg0mrAY8eZqqgCfQRUwKqPRpEr8c+VK6d5OssgD EIsAoJEMDc3oAw9hosNZfPs0jpvM0Imw =tHFH -----END PGP SIGNATURE----- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Jun-30 13:49 UTC
Re: [Xen-users] [Fwd: DomUs don''t shutdown with cpu-pinning configured]
On Tue, Jun 30, 2009 at 5:35 PM, Joern Bredereck<jb@bw-networx.net> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > since pinning the cpu cores to Dom0 and the DomUs the shutdown of the > VMs doesn''t work anymore. When shutting down or rebooting a DomU the > DomU just freezes after the shutdown process but won''t reboot or stop > the DomU. The shutdown itself seems to be complete though.As I recall there were some problems related with cpu pin, which seems to be version or distro-specific. Perhaps this is one of them.> Some info about our setup: > > root@xen1:~# uname -a > Linux xen1 2.6.24-24-xen #1 SMP Wed Apr 15 17:05:38 UTC 2009 x86_64 > GNU/Linux > > root@xen1:~# dpkg -l |grep xen > ii libxen3 3.3.0-1ubuntu7~hardy1> Any idea how to fix this issue?One way is to not use Ubuntu :P Another way is to try compiling Xen from source first. You should be able to use either Ubuntu''s/Debian''s/Xen.org''s kernel, whichever works better for you. I use RHEL boxes with RH''s Xen 3.1 or Gitco''s Xen 3.3.1 and 3.4, with RH''s kernel-xen. Cpu pin works fine on those systems. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users