From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Frame buffer corruptions with KVM >= 2.6.36 Date: Thu, 14 Oct 2010 14:31:08 +0200 Message-ID: <4CB6F80C.8050202@redhat.com> References: <4CB6B0FB.7080100@web.de> <4CB6F33E.3020009@siemens.com> <4CB6F3F1.9060409@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm , Takuya Yoshikawa To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:24328 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753471Ab0JNMbS (ORCPT ); Thu, 14 Oct 2010 08:31:18 -0400 In-Reply-To: <4CB6F3F1.9060409@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/14/2010 02:13 PM, Avi Kivity wrote: > >> and this commit just makes the >> corruptions more likely. This may even be a QEMU issue in the cirrus/vga >> model (both qemu-kvm and upstream show the effect). >> > > What about -no-kvm? > Doesn't happen there. My guess is the initial dirty log after the switch does not contain all 1s so memory isn't updated. Probably need to force a full redraw in that case. -- error compiling committee.c: too many arguments to function