From: Avi Kivity <avi@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: "KVM internal error. Suberror: 1" with ancient 2.4 kernel as guest
Date: Tue, 31 Aug 2010 19:30:39 +0300 [thread overview]
Message-ID: <4C7D2E2F.6050509@redhat.com> (raw)
In-Reply-To: <4C7D2473.6090106@redhat.com>
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.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-31 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 14:32 "KVM internal error. Suberror: 1" with ancient 2.4 kernel as guest Jiri Kosina
2010-08-31 15:49 ` Avi Kivity
2010-08-31 16:30 ` Avi Kivity [this message]
2011-03-21 21:23 ` Wei Xu
2011-03-22 10:54 ` Jiri Kosina
2011-03-25 22:12 ` Wei Xu
2011-03-27 11:57 ` Avi Kivity
2011-03-28 0:53 ` Wei Xu
2011-03-28 9:23 ` Avi Kivity
2011-03-28 16:31 ` Wei Xu
2011-03-28 16:33 ` Avi Kivity
2011-03-28 16:36 ` Wei Xu
2011-03-28 0:54 ` Wei Xu
2011-03-28 9:24 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C7D2E2F.6050509@redhat.com \
--to=avi@redhat.com \
--cc=jkosina@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).