From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm-userspace: VGA/VESA framebuffer broken Date: Fri, 05 Dec 2008 12:19:11 +0200 Message-ID: <4939001F.5080408@redhat.com> References: <4938FCA8.3010408@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Glauber Costa , kvm-devel To: Jan Kiszka Return-path: Received: from mx2.redhat.com ([66.187.237.31]:42234 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751692AbYLEKTF (ORCPT ); Fri, 5 Dec 2008 05:19:05 -0500 In-Reply-To: <4938FCA8.3010408@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka wrote: > Hi, > > latest kvm-userspace git 6892f63c18a526c7b54bbde2f59287787eabe1f8 > appears to have a bug /wrt VGA/VESA modes. I just fired up one of my > Linux test kernels which runs a framebuffer console in mode 0x317, but > the display just contains garbage. Reverting to > 82daa70a1d5bcad3a93150ffc5afbcb9e77361fb makes the problem disappear again. > > I also tried latest qemu with -enable-kvm against the same kernel > modules, and the result is somehow better in that there is some output > on the screen -- but it is horribly slow. > > Glauber, Avi, is this a problem of latest qemu upstream changes to the > vga emulation or a merge issue? > It's caused by the recent merge; qemu upstream now has vga dirty bit tracking, done in a different way from kvm-userspace.git. I've got it fixed here, just need to test a bit more. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.