From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BP3Hx-00043y-Qm for qemu-devel@nongnu.org; Sat, 15 May 2004 13:49:33 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BP3Fz-0001w7-U6 for qemu-devel@nongnu.org; Sat, 15 May 2004 13:48:08 -0400 Received: from [66.111.4.26] (helo=out2.smtp.messagingengine.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BP3Fl-0001aY-Ld for qemu-devel@nongnu.org; Sat, 15 May 2004 13:47:17 -0400 Received: from server3.messagingengine.com (server3.internal [10.202.2.134]) by mail.messagingengine.com (Postfix) with ESMTP id 3FA10B84B3C for ; Sat, 15 May 2004 13:47:14 -0400 (EDT) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" MIME-Version: 1.0 From: list-qemu@alias.spaceandtime.org Date: Sat, 15 May 2004 12:47:15 -0500 Message-Id: <1084643235.17753.196529926@webmail.messagingengine.com> Subject: [Qemu-devel] clock timer configuration lost probably a VIA686a 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 According to Alan Cox, this is a bug in 2.2 kernels. Here is another bit of information from the vmware.guest.linux newsgroup: http://groups.google.com/groups?q=clock+timer+configuration+lost+-+probably+a++clock+timer+configuration+lost+VIA686a&hl=en&lr=&ie=UTF-8&oe=UTF-8&scoring=d&selm=20040317223444.71a5da39%40giga.mumblefrotz.org&rnum=3 Apparently many virtualization/emulators have the same issue. I can confirm that upgrading to 2.4 eliminates the problem.