Andy Smith
2009-Feb-21 18:19 UTC
[Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
Hi, Since upgrading to Debian''s 3.2-1 hypervisor package, domains do not cleanly shutdown or reboot anymore. They remain in the "s" state until destroyed manually, then it is possible to create them again. Here is a snippet of console output from a domain which has been told to shut down: Stopped /var/www/vhcs2/daemon/vhcs2_daemon (pid 7773). Asking all remaining processes to terminate...All processes ended within 1 seconds....done. done. .Deconfiguring network interfaces...Cleaning up ifupdown...Will now deactivate swap:. done. [160455.177159] System halted. In the other window, "xm shutdown -w" returns believing that the domain has been shut down, but it hasn''t. "xm list" says: Name ID Mem VCPUs State Time(s) test4 48 480 1 ---s-- 1329.4 "xm list --long test4" confirms that on_poweroff is set to destroy: (domain (domid 48) (on_crash restart) (uuid 840a911c-49dc-9b25-88b0-49d17e538e37) (bootloader_args ) (vcpus 1) (name test4) (on_poweroff destroy) (on_reboot restart) ...etc... This happens with every domain, but this behaviour was not seen before the upgrade. Any ideas? Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Feb-21 22:38 UTC
Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
On Sun, Feb 22, 2009 at 1:19 AM, Andy Smith <andy@strugglers.net> wrote:> Since upgrading to Debian''s 3.2-1 hypervisor package, domains do not > cleanly shutdown or reboot anymore. They remain in the "s" state > until destroyed manually, then it is possible to create them again.Have you reboot your system since the upgrade? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Smith
2009-Feb-21 23:41 UTC
Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
Hi Fajar, On Sun, Feb 22, 2009 at 05:38:57AM +0700, Fajar A. Nugraha wrote:> On Sun, Feb 22, 2009 at 1:19 AM, Andy Smith <andy@strugglers.net> wrote: > > Since upgrading to Debian''s 3.2-1 hypervisor package, domains do not > > cleanly shutdown or reboot anymore. They remain in the "s" state > > until destroyed manually, then it is possible to create them again. > > Have you reboot your system since the upgrade?Yes. Otherwise how would it be running the newer hypervisor? Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Feb-22 07:47 UTC
Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
On Sun, Feb 22, 2009 at 6:41 AM, Andy Smith <andy@strugglers.net> wrote:>> Have you reboot your system since the upgrade? > > Yes. Otherwise how would it be running the newer hypervisor?I had a similar problem with different version of Xen, and it turned out it''s simply because I forgot to reboot the server, leaving Xen userland and hypervisor mismatch :) Anyway, for your particular situation you could try : - making sure hypervisor and userland match. Perhaps something screwed up your installation. OR, - update to a version of Xen known to work. I''m using Xen 3.3.1 on RHEL and it works correctly. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James Harper
2009-Feb-22 11:36 UTC
RE: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
> > On Sun, Feb 22, 2009 at 6:41 AM, Andy Smith <andy@strugglers.net>wrote:> >> Have you reboot your system since the upgrade? > > > > Yes. Otherwise how would it be running the newer hypervisor? > > I had a similar problem with different version of Xen, and it turned > out it''s simply because I forgot to reboot the server, leaving Xen > userland and hypervisor mismatch :) > > Anyway, for your particular situation you could try : > - making sure hypervisor and userland match. Perhaps something screwed > up your installation. OR, > - update to a version of Xen known to work. I''m using Xen 3.3.1 on > RHEL and it works correctly. >There is a bug in 3.3.1 that comes about when you have more than one CPU and you restrict Dom0 to one CPU by putting "(dom0-cpus 1)" in your config file. The symptoms are that the domain won''t shut down until you do an ''xm start'' again, and even then bits of it hang around in the hypervisor. I''m not sure if that bug existed in 3.2 though. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Philipp Schmid
2009-Feb-22 12:12 UTC
[Xen-devel] Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
On Feb 22, 2009, at 12:36 PM, James Harper wrote:> There is a bug in 3.3.1 that comes about when you have more than one > CPU > and you restrict Dom0 to one CPU by putting "(dom0-cpus 1)" in your > config file. The symptoms are that the domain won''t shut down until > you > do an ''xm start'' again, and even then bits of it hang around in the > hypervisor. > > I''m not sure if that bug existed in 3.2 though.It seems so: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1326 As I''m running into the same problem, is there a known fix or does anyone has an idea where to start debugging this problem? Lg Philipp _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Fajar A. Nugraha
2009-Feb-22 12:25 UTC
Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
On Sun, Feb 22, 2009 at 6:36 PM, James Harper <james.harper@bendigoit.com.au> wrote:> There is a bug in 3.3.1 that comes about when you have more than one CPU > and you restrict Dom0 to one CPU by putting "(dom0-cpus 1)" in your > config file. The symptoms are that the domain won''t shut down until you > do an ''xm start'' again, and even then bits of it hang around in the > hypervisor. > > I''m not sure if that bug existed in 3.2 though.Okay. Now that''s just plain weird. I use RHEL 5.3 x86_64, Xen 3.3.1 from Gitco, (dom0-cpus 1), (dom0-min-mem 256), and dom0_mem=512M dom0_vcpus_pin. I''ve been using both PV Linux and HVM Windows domUs on it and they can shutdown and reboot just fine. Any ideas where this bug is located? Is it the hypervisor, kernel, or userland tools? If what you''re saying is true (in that the bug affects 3.3.1 as well) then my only guess is that somehow my setup is immune to this bug. I''d really like to know how. Regards, Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andy Smith
2009-Feb-23 21:45 UTC
Re: [Xen-users] Domains do not shut down or reboot cleanly since upgrade to 3.2-1
Hi, On Sun, Feb 22, 2009 at 01:12:28PM +0100, Philipp Schmid wrote:> On Feb 22, 2009, at 12:36 PM, James Harper wrote: > >There is a bug in 3.3.1 that comes about when you have more than > >one CPU and you restrict Dom0 to one CPU by putting "(dom0-cpus > >1)" in your config file. The symptoms are that the domain won''t > >shut down until you do an ''xm start'' again, and even then bits > >of it hang around in the hypervisor. > > > >I''m not sure if that bug existed in 3.2 though. > > It seems so: > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1326Well if allowing dom0 to use all CPUs avoids this problem then that''s what I''ll do. I guess we''ll see after the next reboot, though I don''t know when that will be. Cheers, Andy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users