From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Fedora 11 PV Xen domU (2.6.29.4-167.fc11.x86_64) crash with invalid opcode in xsave_cntxt_init (xsetbv) Date: Mon, 21 Sep 2009 13:29:21 -0700 Message-ID: <4AB7E221.60709@goop.org> References: <20090921195750.GQ31123@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090921195750.GQ31123@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com, fedora-xen@redhat.com List-Id: xen-devel@lists.xenproject.org On 09/21/09 12:57, Pasi K=E4rkk=E4inen 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 wonderin= g > 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=3D/dex/xvda1 ro earlyprintk=3Dxen > (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:[] (early) [] xs= ave_cntxt_init+0xba/0x199 > =20 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.=20 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