From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: reboot code (was: boot options for xen) Date: Mon, 12 Sep 2005 18:24:19 -0700 Message-ID: References: Reply-To: kip.macy@gmail.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1048713639==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: James Harper Cc: Xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1048713639== Content-Type: multipart/alternative; boundary="----=_Part_19942_1568038.1126574659821" ------=_Part_19942_1568038.1126574659821 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline If you add "noreboot" you need to power-cycle by hand. -Kip On 9/9/05, James Harper wrote: >=20 > > > '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=3Doff on the Xen command line. >=20 > 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. >=20 > 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. >=20 > 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? >=20 > Thanks >=20 > James >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > ------=_Part_19942_1568038.1126574659821 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 doanything
> > useful now though.
>
> It doesn;t exist = as an option any more. You could try nosmp and/or
> acpi=3Doff 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 kernelpanicked. The annoying thing was that it hung on reboot.

Has xen c= hanged the way it does a reboot between=20 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 cause= d
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
<= br> ------=_Part_19942_1568038.1126574659821-- --===============1048713639== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1048713639==--