Almighty Repo Maintainers, I believe the current repository version of Xen for Lenny stable may be afflicted with this bug, which prevents domUs from shutting down/rebooting properly. http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00050.html What say you? Best Regards Nathan Eisenberg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20090730/2d71ef90/attachment.htm>
On Thu, Jul 30, 2009 at 05:22:24PM -0700, Nathan Eisenberg wrote:> Almighty Repo Maintainers, > > I believe the current repository version of Xen for Lenny stable may be afflicted with this bug, which prevents domUs from shutting down/rebooting properly. > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00050.html > > What say you? >Most probably the 2.6.26 kernel in lenny is affected of that bug. The fix that went into linux-2.6.18-xen.hg in January 2009 is this: http://xenbits.xen.org/linux-2.6.18-xen.hg?rev/79e82ae1bad0 Has anyone tracked down the other bugs in lenny's 2.6.26-xen? live migrations are reported to be broken on some setups, the dom0 kernel crashing on newer hypervisors (3.3 and 3.4). I've seen users report at least those. -- Pasi
Nathan Eisenberg schreef:> Almighty Repo Maintainers, > > I believe the current repository version of Xen for Lenny stable may > be afflicted with this bug, which prevents domUs from shutting > down/rebooting properly. > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00050.htmlMy domU's did not reboot too, after a reboot of the dom0. But this was because the dom0 saved the domU memory in /var. See my postings about the time-problem. After a hard reboot of the domU's with "xm destroy <name>", rebooting is no problem anymore (and the time-problem is fixed too). Maybe this helps you too. I think I will do a "xm shutdown -a" before rebooting my dom0, in the future. With regards, Paul van der Vlis. -- http://www.vandervlis.nl/