Hi,
those are our on_* settings:
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
the same config file works as expected on a debian etch host with xen
3.3.1.
But I have I've got a bit farther to the problem now:
If I reboot a domU from within the domU it hangs on state s after
shutdown
It will hang there forever until I create another domain. If I create
another domain, the one hanging at state s also gets started again.
It won't work with destroying another domain.
I have attached the xend.log output from the following scenario:
create domU: g-m5t12oln
reboot domU g-m5t12oln from within vm
(g-m5t12oln hangs on state s now)
create domU: g-nbjaohbe
(g-m5t12oln starts too now)
reboot domU g-nbjaohbe from within vm
(g-nbjaohbe hangs on state s now)
destroy g-m5t12oln
(g-nbjaohbe still hangs on state s)
create domU: g-m5t12oln
(g-nbjaohbe starts too now)
Lg Philipp
xend_output.txt
Description: Text document
On Feb 17, 2009, at 1:46 PM, Fajar A. Nugraha wrote:
On Tue, Feb 17, 2009 at 6:42 PM, Philipp Schmid <lists@xxxxxxxxxxx>
wrote:
after I type "reboot" within the vm, the vm shuts down properly,
but then
never boots up again:
any idea what the problem could be or how I could debug it, to nail
down the
cause?
What does /var/log/xen/xend.log say?
Do you have any "on_reboot" line on your domU config file?
Regards,
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home