From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wei Xu <wexu2@cisco.com>
Subject: Re: "KVM internal error. Suberror: 1" with ancient 2.4 kernel as
 guest
Date: Mon, 21 Mar 2011 14:23:40 -0700
Message-ID: <C9AD0FEC.2A95F%wexu2@cisco.com>
References: <4C7D2E2F.6050509@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>, <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>, Jiri Kosina <jkosina@suse.cz>
Return-path: <kvm-owner@vger.kernel.org>
Received: from sj-iport-5.cisco.com ([171.68.10.87]:4195 "EHLO
	sj-iport-5.cisco.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754239Ab1CUVYD (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 21 Mar 2011 17:24:03 -0400
In-Reply-To: <4C7D2E2F.6050509@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi and Jiri:

I implemented emulation of movq(64bit) and movdqa(128 bit). If you guys
still need it let me know and I can post somewhere...

Wei Xu


On 8/31/10 9:30 AM, "Avi Kivity" <avi@redhat.com> wrote:

> 
>   On 08/31/2010 06:49 PM, Avi Kivity wrote:
>>  On 08/31/2010 05:32 PM, Jiri Kosina wrote:
>>> (qemu) x/5i $eip
>>> 0x00000000c027a841:  movq   (%esi),%mm0
>>> 0x00000000c027a844:  movq   0x8(%esi),%mm1
>>> 0x00000000c027a848:  movq   0x10(%esi),%mm2
>>> 0x00000000c027a84c:  movq   0x18(%esi),%mm3
>>> 0x00000000c027a850:  movq   %mm0,(%edx)
>>> ===
>>> 
>>> Is there any issue with emulating MMX?
>>> 
>> 
>> Yes.  MMX is not currently emulated.
>> 
>> If there's a command line option to disable the use of MMX you can try
>> it, otherwise wait for it to be implemented (or implement it
>> yourself).  I'll try to do it for 2.6.37, but can't promise anything.
> 
> You can also run qemu with -cpu qemu32,-mmx.  That will expose a cpu
> without mmx support; hopefully the guest kernel will see that and avoid
> mmx instructions.