From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EZtnj-0002KC-VU for qemu-devel@nongnu.org; Wed, 09 Nov 2005 12:32:00 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EZtng-0002JK-0X for qemu-devel@nongnu.org; Wed, 09 Nov 2005 12:31:59 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EZtnf-0002JG-TX for qemu-devel@nongnu.org; Wed, 09 Nov 2005 12:31:55 -0500 Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1EZtnf-00054e-PB for qemu-devel@nongnu.org; Wed, 09 Nov 2005 12:31:56 -0500 Date: Wed, 9 Nov 2005 18:31:53 +0100 (MET) From: space-wizard@gmx.de MIME-Version: 1.0 Message-ID: <10145.1131557513@www63.gmx.net> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: timing problems 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 Hi! I checked my QEMU and I found the same Problems. I'm running SLES9 (x86) on an SLES9 (ppc) host. The target clock runs faster(? I've got positive offsets running ntpdate ?) than the host clock. I've tried severel kernel parameters (eg. clock=pit or clock=pmtmr) without any success. The timing problems seem to be not only a problem with Windows XP as guest os. Best regards christoph -- Highspeed-Freiheit. Bei GMX supergünstig, z.B. GMX DSL_Cityflat, DSL-Flatrate für nur 4,99 Euro/Monat* http://www.gmx.net/de/go/dsl