From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JINGx-0005yp-Pf for qemu-devel@nongnu.org; Fri, 25 Jan 2008 07:03:03 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JINGu-0005wJ-An for qemu-devel@nongnu.org; Fri, 25 Jan 2008 07:03:03 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JINGu-0005wA-85 for qemu-devel@nongnu.org; Fri, 25 Jan 2008 07:03:00 -0500 Received: from wx-out-0506.google.com ([66.249.82.230]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JINGt-0003Mm-Qn for qemu-devel@nongnu.org; Fri, 25 Jan 2008 07:02:59 -0500 Received: by wx-out-0506.google.com with SMTP id h31so476443wxd.4 for ; Fri, 25 Jan 2008 04:02:59 -0800 (PST) Message-ID: Date: Fri, 25 Jan 2008 19:02:58 +0700 From: "Mulyadi Santosa" Subject: Re: [Qemu-devel] Slow clock in guest OS In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8122F5B3F5384F6EB9822FC6673E6BA3@intranet> 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... On Jan 25, 2008 6:51 PM, Sergey Bychkov wrote: > Yes, it helps, in some extent. > With rtc/max-user-freq set to 1024 and "-clock rtc" option VM now works like > in 0.8.2 version. > Clock is slower than in host, but Windows Time server could correct this, if > started. > Busy host or guest CPU slows down clock. I remember somebody wrote dyntick patch...but not sure if it is already merged into qemu CVS. Maybe you need similar trick like win98 to halt CPU when not doing anything? > Sometimes VM hangs on start. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this is weird.... can you dump the generated opcode? pls see qemu-doc/tech for more detail on how to do it. >Htop shows that qemu uses 100% of second CPU in > user mode. Before I forgot, do you use kqemu? if yes, do you full virtualization mode? >Internal QEMU VNC server listens port but doesn't accepts > connections, so vncviewer hangs too. If used GUI, is shows monitor prompt, > that doesn't accept any keyboard input. Could be killed by Ctrl-C in console > or 'kill -9'. May be it's different problem but they happen both on the same > host hardware. > very weird....do you use precompiled qemu binary? or do you compile by yourself? if it is compiled by yourself, what gcc version do you use? regards, Mulyadi.