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

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

  • To: "Philipp Hahn" <hahn@xxxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Likarpenkov Alexander" <al@xxxxxxxxxxxxxxx>
  • Date: Thu, 26 Jan 2012 13:17:16 +0200
  • Delivery-date: Thu, 26 Jan 2012 11:18:31 +0000
  • Fl-build: Fidolook 2002 (SL) 6.0.2800.94 - 5/4/2005 11:39:16
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I also got into sitatsiyu when dom0 is half dead condition. And besides reset button - nothing could help me. What to do when dom0 freezes? How to override it with the commands if there is still an open server console but xend does not work anymore?

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

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

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

PH> Any help is appreciated.

I try to select the top of the correspondence
and collected  in one location.
Come and help comments

Xen-users mailing list



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