Greetings list! I have a Debian Lenny (stable) Dom0 running 3.2.1 (repository version). I have used xen-create-image with -install-method rinse to create a Centos 5 domU. I had to add the usual packages to the rinse configuration to get this to work properly. Things are working great - except that when I reboot the domU, it just puts the domU into a blocked state, and never actually reboots. The console messages for the domU are: Sending all processes the TERM signal... Sending all processes the KILL signal... Saving random seed: Syncing hardware clock to system time Turning off swap: Please stand by while rebooting the system... [ 36.318023] Restarting system. And it stays at this point until the domU is destroyed and recreated. Anyone have any thoughts? Best Regards Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Expanding on this a bit further, here is the output of xm list # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 489 1 r----- 260.5 centosvm 12 1000 2 ---s-- 7.2 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m having similar problems with some Lenny guests. One of them reboots fine, the others show the "Restarting system" message but stay powered off then (not blocked). If anyone has a solution, I''d like to know the answer too ;) Nathan Eisenberg wrote:> > Greetings list! > > > > I have a Debian Lenny (stable) Dom0 running 3.2.1 (repository > version). I have used xen-create-image with --install-method rinse to > create a Centos 5 domU. I had to add the usual packages to the rinse > configuration to get this to work properly. > > > > Things are working great -- except that when I reboot the domU, it > just puts the domU into a blocked state, and never actually reboots. > > > > The console messages for the domU are: > > > > Sending all processes the TERM signal... > > Sending all processes the KILL signal... > > Saving random seed: > > Syncing hardware clock to system time > > Turning off swap: > > Please stand by while rebooting the system... > > [ 36.318023] Restarting system. > > > > And it stays at this point until the domU is destroyed and recreated. > > > > Anyone have any thoughts? > > > > Best Regards > > Nathan Eisenberg > > Sr. Systems Administrator > > Atlas Networks, LLC > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tried creating a i386 domU using a manual rinse rather than xen-create-image (the old ones are amd64). I''m still having this issue - the new domains are getting stuck in the ''s'' state after a reboot. Best Regards Nathan Eisenberg> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of Nathan Eisenberg > Sent: Wednesday, July 29, 2009 2:40 PM > To: XenUsers > Subject: [Xen-users] RE: DomU reboot issues > > Expanding on this a bit further, here is the output of xm list > > # xm list > Name ID Mem VCPUs State > Time(s) > Domain-0 0 489 1 r----- > 260.5 > centosvm 12 1000 2 ---s-- > 7.2 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
A further update - I built a clean Debian system on different hardware, installed the repository version of XEN, and created a Debian domU. Rebooting the domU results in the same behavior - the domU just sits there in an almost dead state. XM list shows the state as being ---s--. Weird. So different hardware, fresh OS, different guest... same behavior. Bugger. Best Regards Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
More digging - I am wondering if I''m running into James Harpers'' evtchn_cpu_notify bug: http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00050.html I''m not sure exactly how to apply the patch, if this is indeed the same bug. Interesting that it made it into the Debian-Stable repository version... Is there a workaround without compiling Xen? Best Regards Nathan Eisenberg Sr. Systems Administrator Atlas Networks, LLC> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of Nathan Eisenberg > Sent: Thursday, July 30, 2009 4:23 PM > To: Xen Users > Subject: [Xen-users] RE: DomU reboot issues > > A further update - I built a clean Debian system on different hardware, > installed the repository version of XEN, and created a Debian domU. > Rebooting the domU results in the same behavior - the domU just sits > there in an almost dead state. XM list shows the state as being ---s-- > . Weird. > > So different hardware, fresh OS, different guest... same behavior. > Bugger. > > Best Regards > Nathan Eisenberg > Sr. Systems Administrator > Atlas Networks, LLC > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users