[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] RFH: Xen crash behaviour Reboot â Stop?


last weekend some production servers running Xen-3.4.3 and Linux-2.6.32 
rebootet. Currently its unclear if the hardware is faulty or if its a 
software problem. Is there an easy way to switch the Xen-hypervisor not to 
reboot the the machine if the dom0 fails?

Doing a test with an "echo c >/proc/sysrq-trigger" crashes the dom0, which 
then makes the the hypervisor to reboot the machine. It would help if the 
system would just stay in that faulty state and not reboot, so one could at 
least look at the screen and see some kernel dump or similar.

I also tried to use kexec, but that doesn't seem to work with Debian 
kexec-tools, which complains about the _dom0_-Kernel not being prepared for 
loading a crashdump kernel, even I pass "crashkernel=512M" via Grub to the 
_hypervisor_. (I really would prefer the Hypervirsor to switch to the 
crashdump kernel instead of just the dom0-kernel, since I also would like to 
get a hypervisor crashdump in addition to only a dom0 crashdump, since I'm 
unsure if the reboot is caused by a faulty dom0 or a Xen hypervisor problem).

Any help is appreciated.

Philipp Hahn           Open Source Software Engineer      hahn@xxxxxxxxxxxxx
Univention GmbH        Linux for Your Business        fon: +49 421 22 232- 0
Mary-Somerville-Str.1  D-28359 Bremen                 fax: +49 421 22 232-99

Attachment: signature.asc
Description: This is a digitally signed message part.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.