From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lqsto-0007di-Gh for qemu-devel@nongnu.org; Mon, 06 Apr 2009 13:46:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lqsti-0007c3-Vv for qemu-devel@nongnu.org; Mon, 06 Apr 2009 13:46:19 -0400 Received: from [199.232.76.173] (port=60714 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lqsti-0007by-T8 for qemu-devel@nongnu.org; Mon, 06 Apr 2009 13:46:14 -0400 Received: from mx2.redhat.com ([66.187.237.31]:56202) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lqsti-0006Q8-E1 for qemu-devel@nongnu.org; Mon, 06 Apr 2009 13:46:14 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n36HkDJO002073 for ; Mon, 6 Apr 2009 13:46:13 -0400 Message-ID: <49DA400B.4060104@redhat.com> Date: Mon, 06 Apr 2009 20:46:51 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [6989] Fix display breakage when resizing the screen (v2) (Avi Kivity) References: <49DA0FFD.1060600@eu.citrix.com> <49DA14A5.4060301@redhat.com> <49DA176B.4090102@redhat.com> <49DA3D7E.5050506@eu.citrix.com> In-Reply-To: <49DA3D7E.5050506@eu.citrix.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Stefano Stabellini wrote: > I tried several times to manually reproduce the issue with no luck: if > no vnc clients are supposed to be connected, how do you make the cirrus > emulated hw do a bitblit? > The guest will boot and do it by itself. > In any case it makes sense that the problem is in qemu_console_copy() > rather than in the rop function itself that only operates on the > emulated framebuffer. > But calling qemu_console_copy() in cirrus_do_copy() shouldn't be risky > because before that, we call vga_hw_update() that should do the resize. > vga_hw_update() may not actually do anything if the conditions are right, and maybe that's the case here. > Without a better understanding of the bug I will refrain from making any > suggestion. > > There's a backtrace in https://bugzilla.redhat.com/show_bug.cgi?id=494002. I'll also try to generate a good scenario for reproducing this. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.