Re: [Xen-devel] VMX status report. Xen: #17320 & Xen0: #500 -- n

To:	"Li, Haicheng" <haicheng.li@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] VMX status report. Xen: #17320 & Xen0: #500 -- no new issue
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Mon, 31 Mar 2008 17:24:53 +0100
Delivery-date:	Mon, 31 Mar 2008 09:26:35 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<FC1D1B23302A22499C60C967336B2AE002952208@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AciTNVxHml+/EsNtRpuJxius/pMMHwAFmOJL
Thread-topic:	[Xen-devel] VMX status report. Xen: #17320 & Xen0: #500 -- no new issue
User-agent:	Microsoft-Entourage/11.4.0.080122

On 31/3/08 14:44, "Li, Haicheng" <haicheng.li@xxxxxxxxx> wrote:

> 4. Hvm guest with generic kernel 2.6.18 cannot boot up.
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1196..

Did you accidentally configure K7 CPU type in your kernel configuration? As
far as I can see that's the only way to end up using __mmx_memcpy().

There's no reason not to emulate MOVQ though, but it'll take me a little
while to work up the patch.

 -- Keir

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

xen-devel

Re: [Xen-devel] VMX status report. Xen: #17320 & Xen0: #500 -- no new is