From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DDcwm-00023Q-3X for qemu-devel@nongnu.org; Tue, 22 Mar 2005 01:33:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DDcwf-00020K-5b for qemu-devel@nongnu.org; Tue, 22 Mar 2005 01:32:53 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DDcwe-0001zB-Kq for qemu-devel@nongnu.org; Tue, 22 Mar 2005 01:32:52 -0500 Received: from [203.190.192.17] (helo=wasp.net.au) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DDcdX-0005u5-Jb for qemu-devel@nongnu.org; Tue, 22 Mar 2005 01:13:07 -0500 Message-ID: <423FB769.7080409@wasp.net.au> Date: Tue, 22 Mar 2005 10:12:57 +0400 From: Brad Campbell MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] WinXp Guest clock drift 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 Does anyone else notice that unless you run an ntp client inside the guest, that time drifts so much/so fast as to be unusable? I work around this by using an ntp client but I thought it worth mentioning. Brad -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams