[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] reboot code (was: boot options for xen)
- To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
- From: Kip Macy <kip.macy@xxxxxxxxx>
- Date: Mon, 12 Sep 2005 18:24:19 -0700
- Cc: Xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Tue, 13 Sep 2005 01:22:11 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=mIQzgz7SoMEsGymmpIp4XeYCH/3w9vi8yKQ4sZkc68gafQzN5NtEj3y8G/NJRoNoT4y//Z+RRG+bgWjVCCM1sQ7+cTxSmx5U283Udiil2lGWoHSTWZUCXvKHxNHCO+gwYqQ9T0DF9pyFZvhMDhHOMiGfcPCU+sWc/fomias9MGc=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
