The problem I was having that xen appeared to have crashed and locked up the machine.
What was actually happening was that xen was doing a
reboot but caused a hang instead. By adding in noreboot,
I could see that xen was just trying to reboot and
not actually crashing.
So if I take noreboot
out, the machine hangs when xen tries to reboot. Xen used
to be able to do a reboot though, hence my question.
Sorry for the confusion.
James
From: Kip Macy
[mailto:kip.macy@xxxxxxxxx]
Sent: Tuesday, 13 September 2005 11:24
To: James Harper
Cc: Keir Fraser;
Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] reboot
code (was: boot options for xen)
If you add "noreboot" you need to power-cycle by hand.
-Kip
On 9/9/05, James
Harper <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> > 'ignorebiostables' got it running again. It doesn't seem to
do
anything
> > useful now though.
>
> It doesn;t exist as an option any more. You could try nosmp and/or
> acpi=off on the Xen command line.
My bad. After adding 'noreboot' I could see that it couldn't mount the
initrd... I'd forgotten to add 'CRAMFS' in my config so the kernel
panicked. The annoying thing was that it hung on reboot.
Has xen changed the way it does a reboot between 2.0.6 and 3.0? This
machine has been able to do a reboot in the past.
I've been bitten by this sort of error before (ie a kernel panic caused
by something I've done wrong but I've missed it because xen rebooted),
could we add in a delay (5 seconds would do, or maybe a boot option)
before xen reboots?
Thanks
James
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
