From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>, kvm@vger.kernel.org
Subject: Re: vga stad / vga vmware leads to KVM internal error. Suberror: 1
Date: Wed, 20 Jan 2010 11:00:24 -0600 [thread overview]
Message-ID: <4B5736A8.9040600@codemonkey.ws> (raw)
In-Reply-To: <4B573366.4000800@redhat.com>
On 01/20/2010 10:46 AM, Avi Kivity wrote:
> On 01/14/2010 04:20 PM, Avi Kivity wrote:
>> On 01/14/2010 04:06 PM, Dominik Brodowski wrote:
>>>
>>>> x/5i $eip
>>> 0x00007f317ab64a7b: movdqa %xmm0,(%rdi)
>>> 0x00007f317ab64a7f: movdqa %xmm0,0x10(%rdi)
>>> 0x00007f317ab64a84: movdqa %xmm0,0x20(%rdi)
>>> 0x00007f317ab64a89: movdqa %xmm0,0x30(%rdi)
>>> 0x00007f317ab64a8e: movdqa %xmm0,0x40(%rdi)
>>>
>>> Same values for "vga vmware" and "vga std".
>>>
>>
>> Yes - this has been reported. We need to start emulating movdqa and
>> a few of its friends.
>>
>
> So I have a nice patchset emulating this instruction (quite a pain,
> since this is the first sse instruction we emulate), but it doesn't
> help. The guest keeps using it so the display is incredibly slow.
>
> Turns out the real problem is somewhere else - the guest is not
> detecting VBE properly so it is forced to use the old slow vga
> access. Not sure what the root cause is.
Is this with -vga std or -vga vmware? Is this a VESA driver in the guest?
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-20 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 14:11 vga std / vga vmware leads to unhandled vm exit: 0x11 Dominik Brodowski
2010-01-13 20:29 ` Dominik Brodowski
2010-01-13 21:59 ` Anthony Liguori
2010-01-13 22:18 ` vga stad / vga vmware leads to KVM internal error. Suberror: 1 Dominik Brodowski
2010-01-14 13:51 ` Avi Kivity
2010-01-14 14:06 ` Dominik Brodowski
2010-01-14 14:20 ` Avi Kivity
2010-01-20 16:46 ` Avi Kivity
2010-01-20 17:00 ` Anthony Liguori [this message]
2010-01-20 17:15 ` Avi Kivity
2010-01-22 13:52 ` Dominik Brodowski
2010-01-24 7:27 ` Avi Kivity
2010-01-24 9:15 ` Dominik Brodowski
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=4B5736A8.9040600@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.