From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DDfjq-0000ZD-8k
	for qemu-devel@nongnu.org; Tue, 22 Mar 2005 04:31:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DDfjP-0000Nj-58
	for qemu-devel@nongnu.org; Tue, 22 Mar 2005 04:31:27 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DDfaH-00070n-8s
	for qemu-devel@nongnu.org; Tue, 22 Mar 2005 04:21:57 -0500
Received: from [69.17.117.25] (helo=mail23.sea5.speakeasy.net)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.34) id 1DDf81-0007iE-Jm
	for qemu-devel@nongnu.org; Tue, 22 Mar 2005 03:52:45 -0500
Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2])
	([64.81.88.222]) (envelope-sender <jhoger@pobox.com>)
	by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
	for <qemu-devel@nongnu.org>; 22 Mar 2005 08:52:42 -0000
Subject: Re: [Qemu-devel] WinXp Guest clock drift
From: "John R. Hogerhuis" <jhoger@pobox.com>
In-Reply-To: <423FD59B.9050808@wasp.net.au>
References: <423FB769.7080409@wasp.net.au>
	<79bf9848050321231566add3e9@mail.gmail.com>
	<aec7e5c3050322001376e25056@mail.gmail.com>
	<423FD59B.9050808@wasp.net.au>
Content-Type: text/plain
Date: Tue, 22 Mar 2005 00:53:03 -0800
Message-Id: <1111481583.15697.182.camel@aragorn>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Tue, 2005-03-22 at 12:21 +0400, Brad Campbell wrote:

> I actually find all sorts of oddities with timing and qemu emulation. Sometimes when installing 
> stuff in a windows guest the guest slows to a crawl until I move the mouse around or drag a window 
> or something similar. Almost like it starts to go to sleep until it gets some user interaction.
> 

FWIW, that is one of those archetypical problems that crops up in event
driven software. It is a sure sign that an event has gone missing or is
being ignored. Events can be interrupts, or data appearing on an
interface that is polled. In this case it would probably have to do with
emulated hardware.

Just a general comment, but maybe it will jog something loose for the
right person...

-- John.