Re: [Xen-devel] kexec regression between 3.1.0 and 3.1.3 ?

[Ward Vandewege <ward@xxxxxxx>]

On Fri, Aug 08, 2008 at 09:06:50AM +0100, Keir Fraser wrote:
> On 8/8/08 01:29, "Ward Vandewege" <ward@xxxxxxx> wrote:
> >>> Any suggestions?
> >> 
> >> Try adding no-real-mode to Xen's command line.
> > 
> > Thank you! That fixes it for 3.1.3 and up (tested 3.1.3, 3.1.4 and 3.2.1).
> 
> It'd be nice to have kexec add that flag by default for Xen, or steal a new
> multiboot flag to mean the same thing, as this trips people up frequently I
> expect. Oh well, hopefully knowledge of this trick will spread.

Yeah.

Is there a significant difference between booting 3.1.4 and 3.2.1 with kexec
in terms of BIOS requirements?

I mentioned that with no-real-mode, I can kexec into a 3.1.3+ Xen kernel
under qemu + bochs bios. I use coreboot (http://coreboot.org) on my servers
though, and it seems that while kexec'ing into 3.1.3 and 3.1.4 works fine
with qemu + coreboot, kexec'ing into 3.2.1 causes qemu to triple-fault and
die.

I tried on real iron this morning (with coreboot), and got similar results:
kexec'ing into 3.1.3 and 3.1.4 works fine now, kexec'ing into 3.2.1 just
hangs the machine.

This is likely a coreboot bug, so I'll have to track that down. Any
information about differences between what 3.2.1 and 3.1.4 require to be
kexec'ed into would be most helpful though.

Thanks,
Ward.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel