This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [Bug] Fix for QEMU 0.8.1 Window Freeze

To: "Huang2, Wei" <Wei.Huang2@xxxxxxx>
Subject: Re: [Xen-devel] [Bug] Fix for QEMU 0.8.1 Window Freeze
From: "Christian Limpach" <christian.limpach@xxxxxxxxx>
Date: Tue, 11 Jul 2006 23:33:54 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Christian Limpach <Christian.Limpach@xxxxxxxxxxxxx>
Delivery-date: Tue, 11 Jul 2006 15:36:16 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HtkOFer3cnCPkbJGBHXJG3deGeI4RXByttQcLLaoLWqSKLjrHTKo4tMAW/5+IOZciilGLFHQzm7nxCsx/XZyYorMgXSiafAG/xZ75Gy2Z/Q7PoNOYHSuQZ3hcgmaAABqIt7SpEnK7KEOQFRjMeWhpsFbb5KYwH8D+fof22Uj2uw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3946CD6D455964280163B82031D3954018C831B@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C3946CD6D455964280163B82031D3954018C831B@xxxxxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 7/11/06, Huang2, Wei <Wei.Huang2@xxxxxxx> wrote:
We had trouble with the latest QEMU 0.8.1 tree
(http://xenbits.xensource.com/chris/xs-tools-ioemu.pq.hg). Basically,
QEMU window appeared but freezed immediately. This happened to both
32-bit and 64-bit hypervisors.

The root cause of this problem is in vnc-fixes patch. It removes
initialization of gui_timer (see below), which actually is used by
gui_update() in vl.c. Retaining these two statements will fix the
problem and QEMU can perform normally.

That's not the root cause because the gui_timer is obselete, or at
least it should be.

gui_update only calls display_state.dpy_refresh but the vnc-fixes
patch also changes vnc_update_client to call dpy_refresh and that gets
called from the vs->timer.

Could you check if somehow the vnc_update_client doesn't get called for you?


diff -r 15da4d2106fe vl.c
--- a/vl.c      Thu Jul 06 14:27:28 2006 +0100
+++ b/vl.c      Thu Jul 06 20:19:49 2006 +0100
@@ -5972,8 +5972,7 @@ int main(int argc, char **argv)
                   kernel_filename, kernel_cmdline, initrd_filename,

-    gui_timer = qemu_new_timer(rt_clock, gui_update, NULL);     <===
-    qemu_mod_timer(gui_timer, qemu_get_clock(rt_clock));        <===
+    display_state.dpy_refresh(&display_state);

     if (use_gdbstub) {

Xen-devel mailing list

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>