Xen users - Dec 2010 - Xen domains will not reboot or destroy as they should be

Hi all,

I''m having a problem with Xen 3.2.1 on Debian 5.0.7 where the Xen
domains will not shutdown or reboot properly. For example, if I do a poweroff
from a paravirtualized domain it just says System halted on the console but
nothing else happens, except the domain status becomes "s". Nothing
gets written into xend.log. I have set on_poweroff = ''destroy''
properly, but it seem to have no effect. Also xm list --long shows the correct
options in use. Same thing happens if I do a reboot. Just get status
"s" and no reboot. Another box installed the same way with same
versions seems to work perfectly. Any ideas?

	-jake

ps. I am not on the list, so please keep my address in the recipients. Thanks.

-- 
Jarkko Santala <jake&portalify,com>   http://www.portalify.com
System Administrator

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

> 
> Hi all,
> 
> I''m having a problem with Xen 3.2.1 on Debian 5.0.7 where the Xen
domains will
> not shutdown or reboot properly. For example, if I do a poweroff from
a
> paravirtualized domain it just says System halted on the console but
nothing
> else happens, except the domain status becomes "s". Nothing gets
written into
> xend.log. I have set on_poweroff = ''destroy'' properly,
but it seem to
have no
> effect. Also xm list --long shows the correct options in use. Same
thing
> happens if I do a reboot. Just get status "s" and no reboot.
Another
box
> installed the same way with same versions seems to work perfectly. Any
ideas?
> 
Do you specify dom0-cpus=1 in your xen config? If so, it causes a
problem that causes events to be missed and things left hanging around
which sounds similar to what you are seeing. I''m not sure about the
version but this sounds very familiar to a bug I encountered once, and
spent ages tracking down.

I highly recommend running a newer version of Xen where this bug is
fixed, but otherwise just don''t specify dom0-cpus=1.

James

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

On Dec 14, 2010, at 12:25 , James Harper wrote:
>> 
>> Hi all,
>> 
>> I''m having a problem with Xen 3.2.1 on Debian 5.0.7 where the
Xen
> domains will
>> not shutdown or reboot properly. For example, if I do a poweroff from
> a
>> paravirtualized domain it just says System halted on the console but
> nothing
>> else happens, except the domain status becomes "s". Nothing
gets
> written into
>> xend.log. I have set on_poweroff = ''destroy''
properly, but it seem to
> have no
>> effect. Also xm list --long shows the correct options in use. Same
> thing
>> happens if I do a reboot. Just get status "s" and no reboot.
Another
> box
>> installed the same way with same versions seems to work perfectly. Any
> ideas?
>> 
> 
> Do you specify dom0-cpus=1 in your xen config? If so, it causes a
> problem that causes events to be missed and things left hanging around
> which sounds similar to what you are seeing. I''m not sure about
the
> version but this sounds very familiar to a bug I encountered once, and
> spent ages tracking down.
> 
> I highly recommend running a newer version of Xen where this bug is
> fixed, but otherwise just don''t specify dom0-cpus=1.
That is indeed true! I had it enabled and I already commented it out, thinking
that it might be causing problems (and it didn''t even work - xentop
still showed dom0 using all 8 logical cores), but I haven''t rebooted
yet, so I didn''t know that it might solve this issue. Thanks!

I don''t know if the same setting is the reason for another bug I ran
into - I tried running some other xm commands instead of destroy on one of these
domains in "s" limbo and what happened was that it started spawning as
many copies of that domU as it could fit into memory - killing them would spawn
another one in the freed memory. The situation finally resolved itself after I
had ran xm destroy in a loop, but I was unable to start any new domUs after that
until I rebooted. Not sure which xm command set it off in the first place.

	-jake



> 
> James
-- 
Jarkko Santala <jake&portalify,com>   http://www.portalify.com
System Administrator




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

2010/12/14 Jarkko Santala <jake@portalify.com>:
> Hi all,
>
> I''m having a problem with Xen 3.2.1 on Debian 5.0.7 where the Xen
domains
> will not shutdown or reboot properly. For example, if I do a poweroff
> from a paravirtualized domain it just says System halted on the console
> but nothing else happens, except the domain status becomes "s".
Hi Jake,

are you using Debian/Squeeze with Kernel
linux-image-2.6.32-5-xen-{amd64|i386}        2.6.32-28
in your DomU?

Last week I had the same problem as you described it.
An update to version 2.6.32-29 resolved it.

HTH

Greetings
Matthias Böttcher

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

On Tue, Dec 14, 2010 at 11:50 AM, Jarkko Santala <jake@portalify.com>
wrote:
>
> I don''t know if the same setting is the reason for another bug I
ran into -
> I tried running some other xm commands instead of destroy on one of these
> domains in "s" limbo and what happened was that it started
spawning as many
> copies of that domU as it could fit into memory - killing them would spawn
> another one in the freed memory. The situation finally resolved itself
after
> I had ran xm destroy in a loop, but I was unable to start any new domUs
> after that until I rebooted. Not sure which xm command set it off in the
> first place.
>
>        -jake
>
> --
> Jarkko Santala <jake&portalify,com>   http://www.portalify.com
> System Administrator
>
>
I have been experiencing same issue with spawning processes of domU. The
solution for this was stopping xend and then killing of all domU-related
processes. Sometimes there were some xenstore entries remaining and I had to
remove them with xenstore-rm before starting domU again.
Unfortunately Debian stable forward-porting Xen kernels are not as stable as
someone would expect and I am thinking of switching to XenSource
''official''
kernel versions.

--
Peter Viskup


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

On Dec 14, 2010, at 12:50 , Jarkko Santala wrote:
> 
> On Dec 14, 2010, at 12:25 , James Harper wrote:
> 
>>> 
>>> Hi all,
>>> 
>>> I''m having a problem with Xen 3.2.1 on Debian 5.0.7 where
the Xen
>> domains will
>>> not shutdown or reboot properly. For example, if I do a poweroff
from
>> a
>>> paravirtualized domain it just says System halted on the console
but
>> nothing
>>> else happens, except the domain status becomes "s".
Nothing gets
>> written into
>>> xend.log. I have set on_poweroff = ''destroy''
properly, but it seem to
>> have no
>>> effect. Also xm list --long shows the correct options in use. Same
>> thing
>>> happens if I do a reboot. Just get status "s" and no
reboot. Another
>> box
>>> installed the same way with same versions seems to work perfectly.
Any
>> ideas?
>>> 
>> 
>> Do you specify dom0-cpus=1 in your xen config? If so, it causes a
>> problem that causes events to be missed and things left hanging around
>> which sounds similar to what you are seeing. I''m not sure
about the
>> version but this sounds very familiar to a bug I encountered once, and
>> spent ages tracking down.
>> 
>> I highly recommend running a newer version of Xen where this bug is
>> fixed, but otherwise just don''t specify dom0-cpus=1.
> 
> That is indeed true! I had it enabled and I already commented it out,
thinking that it might be causing problems (and it didn''t even work -
xentop still showed dom0 using all 8 logical cores), but I haven''t
rebooted yet, so I didn''t know that it might solve this issue. Thanks!
I have now rebooted the box and it seems that this was indeed the problem. Now
that dom0-cpus is set back to 0 domains are rebooting normally.

I gave testing/squeeze a quick look, updating an unused Debian 5 Xen box, but it
seemed like a bit of a hassle at this time, even though 4.0 does seem tempting.
Hopefully they''ll get 6 released sooner than later.

	-jake
> I don''t know if the same setting is the reason for another bug I
ran into - I tried running some other xm commands instead of destroy on one of
these domains in "s" limbo and what happened was that it started
spawning as many copies of that domU as it could fit into memory - killing them
would spawn another one in the freed memory. The situation finally resolved
itself after I had ran xm destroy in a loop, but I was unable to start any new
domUs after that until I rebooted. Not sure which xm command set it off in the
first place.
> 
> 	-jake
> 
> 
> 
> 
>> 
>> James
> 
> -- 
> Jarkko Santala <jake&portalify,com>   http://www.portalify.com
> System Administrator
> 
> 
> 
-- 
Jarkko Santala <jake&portalify,com>   http://www.portalify.com
System Administrator




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