[Xen-devel] Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv)

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

On 09/21/09 12:57, Pasi Kärkkäinen wrote:
> Hello Jeremy and others,
>
> I friend of mine is trying to install x86_64 Fedora 11 Xen PV domU on
> CentOS 5.4 x86_64 dom0. He's getting a kernel crash.. so I was wondering
> if you've seen this one before.
>
> A couple of kernel boot/crash logs:
> http://v6.fi/misc/f11_64_kernel.debug2.txt
> http://v6.fi/misc/f11_64_kernel.debug4.txt
>
> (early) Kernel command line:  root=/dex/xvda1 ro earlyprintk=xen
> (early) Initializing CPU#0
> (early) invalid opcode: 0000 [#1] (early) SMP (early)
> (early) last sysfs file:
> (early) CPU 0 (early)
> (early) Modules linked in:(early)
> (early) Pid: 0, comm: swapper Not tainted 2.6.29.4-167.fc11.x86_64 #1
> (early) RIP: e030:[<ffffffff81397963>] (early)  [<ffffffff81397963>] 
> xsave_cntxt_init+0xba/0x199
>   

This looks like the bug where Xen doesn't filter out the xsave feature
flag and the kernel tries to use it, fixed in change ef7616ff29ad. 
Kernel change  e826fe1ba15 works around the Xen bug by doing its own
masking (I think it got into 2.6.30).

There's also a "noxsave" kernel parameter, but that may have been added
after 2.6.29.

    J

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