From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: vga stad / vga vmware leads to KVM internal error. Suberror: 1 Date: Wed, 20 Jan 2010 19:15:02 +0200 Message-ID: <4B573A16.6050304@redhat.com> 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> <4B5736A8.9040600@codemonkey.ws> 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: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:59699 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752213Ab0ATRPJ (ORCPT ); Wed, 20 Jan 2010 12:15:09 -0500 In-Reply-To: <4B5736A8.9040600@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 01/20/2010 07:00 PM, Anthony Liguori wrote: >> 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? Yes (both reported, I confirmed with -vga std). > Is this a VESA driver in the guest? So it seems from the Xorg log. Boot a Ubuntu 9.10 cdrom, on qemu-kvm-0.11 it boots fine and fast, on 0.12 it fails on emulation (unless you apply my patchset, in which case it works, but is incredibly slow). -- error compiling committee.c: too many arguments to function