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:38:54 +0200 Message-ID: <4CB6F9DE.6060008@redhat.com> References: <4CB6B0FB.7080100@web.de> <4CB6F33E.3020009@siemens.com> <4CB6F3F1.9060409@redhat.com> <4CB6F932.8030605@siemens.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]:39904 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753989Ab0JNMjA (ORCPT ); Thu, 14 Oct 2010 08:39:00 -0400 In-Reply-To: <4CB6F932.8030605@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/14/2010 02:36 PM, Jan Kiszka 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? > > Just booted it (took ages), and the result was actually a completely > black screen. Kind of persistent corruption. This really looks like a > qemu issue now, maybe even a regression as I don't remember running into > such effects a while back. Worked fine for me (though yes it was slow - did tcg regress?). -- error compiling committee.c: too many arguments to function