* RE: reboot code (was: boot options for xen)
@ 2005-09-10 0:15 James Harper
2005-09-13 1:24 ` Kip Macy
0 siblings, 1 reply; 3+ messages in thread
From: James Harper @ 2005-09-10 0:15 UTC (permalink / raw)
To: Keir Fraser; +Cc: Xen-devel
> > '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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: reboot code (was: boot options for xen)
2005-09-10 0:15 reboot code (was: boot options for xen) James Harper
@ 2005-09-13 1:24 ` Kip Macy
0 siblings, 0 replies; 3+ messages in thread
From: Kip Macy @ 2005-09-13 1:24 UTC (permalink / raw)
To: James Harper; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
If you add "noreboot" you need to power-cycle by hand.
-Kip
On 9/9/05, James Harper <james.harper@bendigoit.com.au> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 1564 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: reboot code (was: boot options for xen)
@ 2005-09-13 1:39 James Harper
0 siblings, 0 replies; 3+ messages in thread
From: James Harper @ 2005-09-13 1:39 UTC (permalink / raw)
To: kip.macy; +Cc: Xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 1784 bytes --]
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@gmail.com]
Sent: Tuesday, 13 September 2005 11:24
To: James Harper
Cc: Keir Fraser; Xen-devel@lists.xensource.com
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@bendigoit.com.au> 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@lists.xensource.com
http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 8460 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-09-13 1:39 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-10 0:15 reboot code (was: boot options for xen) James Harper
2005-09-13 1:24 ` Kip Macy
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 1:39 James Harper
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.