From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: vga stad / vga vmware leads to KVM internal error. Suberror: 1 Date: Wed, 20 Jan 2010 11:00:24 -0600 Message-ID: <4B5736A8.9040600@codemonkey.ws> References: <20091214141155.GA4886@comet.dominikbrodowski.net> <20100113202956.GA9075@comet.dominikbrodowski.net> <4B4E4245.1020100@codemonkey.ws> <20100113221802.GA27280@comet.dominikbrodowski.net> <4B4F216F.2070009@redhat.com> <20100114140631.GA5836@comet.dominikbrodowski.net> <4B4F2828.8010200@redhat.com> <4B573366.4000800@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dominik Brodowski , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mail-yw0-f198.google.com ([209.85.211.198]:60211 "EHLO mail-yw0-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751676Ab0ATRA1 (ORCPT ); Wed, 20 Jan 2010 12:00:27 -0500 Received: by ywh36 with SMTP id 36so4570414ywh.15 for ; Wed, 20 Jan 2010 09:00:27 -0800 (PST) In-Reply-To: <4B573366.4000800@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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