From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40300) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WT5s7-0006Bw-RJ for qemu-devel@nongnu.org; Thu, 27 Mar 2014 04:41:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WT5s0-0007sb-Gw for qemu-devel@nongnu.org; Thu, 27 Mar 2014 04:41:11 -0400 Received: from moutng.kundenserver.de ([212.227.126.131]:63552) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WT5s0-0007sD-72 for qemu-devel@nongnu.org; Thu, 27 Mar 2014 04:41:04 -0400 Message-ID: <5333E41E.2050803@rdsoftware.de> Date: Thu, 27 Mar 2014 09:41:02 +0100 From: Erik Rull MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Missing guest clock-sync on Host clock change List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" Hi all, I would like to have the guest "drifting" to a new set clock on the host. My problem is the following: - Host System (Linux) starts up, hwclock and kernel time are synced, guest starts up with -rtc clock=host,driftfix=slew (which I assume should fix any drift issue on ACPI compatible guest OSes) - Host System kernel time drifts against the hwclock (jiffies timer due to no other available useful timer on SMP systems - core2duo has no hpet!) - calling "hwclock -s" on the host resyncs the kernel time with the hwclock, so "date" and "hwclock" show the same again - the guest stays at the "old" kernel time before the sync - also after 1 hour the delta is still the same, so no sync or slew is done :-( My guest OS is Windows 8, which must have ACPI enabled, otherwise it will not work. Any ideas how to proceed? Maybe some command line parameters are wrong? I need this resync for the guest due to external synchronization - it must not be millisecond-precise, but a 9 seconds shift during a run overnight is too much! Thanks. Best regards, Erik