From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: Frame buffer corruptions with KVM >= 2.6.36
Date: Thu, 14 Oct 2010 14:04:58 +0200
Message-ID: <4CB6F1EA.6010309@redhat.com>
References: <4CB6B0FB.7080100@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:55438 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753498Ab0JNMFC (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 14 Oct 2010 08:05:02 -0400
In-Reply-To: <4CB6B0FB.7080100@web.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

  On 10/14/2010 09:27 AM, Jan Kiszka wrote:
> Hi,
>
> I'm seeing quite frequent corruptions of the VESA frame buffer with
> Linux guests (vga=0x317) that are starting with KVM kernel modules of
> upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
> downgrading to kvm-kmod-2.6.35.6. Will see if I can bisect later, but
> maybe someone already has an idea or wants to reproduce (just run
> something like "find /" on one text console and witch to another one -
> text fragments will remain on the screen on every few switches).
>

Reproduces on kvm.git.  I wonder what's going on.

Looks like vesafb uses the bios to switch the display start, so I expect 
a problem in qemu reacting to this.

-- 
error compiling committee.c: too many arguments to function