[Xen-devel] Re: Failure to load 2.6.29-rc7 under Xen Unstable on

To:	Boris Derzhavets <bderzhavets@xxxxxxxxx>, "Marc - A. Dahlhaus" <mad@xxxxxx>
Subject:	[Xen-devel] Re: Failure to load 2.6.29-rc7 under Xen Unstable on Q9550 & ASUS P5Q-E box
From:	Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date:	Sat, 07 Mar 2009 10:06:21 -0800
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Sat, 07 Mar 2009 10:06:59 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Hm, it looks like its trying to enable extended fpu/sse state (cr4.oxsave); I'm 
not sure if Xen supports that. I would have thought that it would mask the 
corresponding cpuid bit if it didn't.

Anyway, it should be fairly easy to sort out once I get in front of a machine. 
In the meantime, perhaps there's a kernel commandline option to stop it from 
trying to do that...

        J
-- 
Sent from my Android phone with K-9. Please excuse my brevity.

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: Failure to load 2.6.29-rc7 under Xen Unstable on Q9550 &