From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44193) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vr8k1-0003cy-Ry for qemu-devel@nongnu.org; Thu, 12 Dec 2013 11:04:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vr8jt-0006QE-EC for qemu-devel@nongnu.org; Thu, 12 Dec 2013 11:03:57 -0500 Received: from mx.ipv6.kamp.de ([2a02:248:0:51::16]:48945 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vr8jt-0006Q6-2E for qemu-devel@nongnu.org; Thu, 12 Dec 2013 11:03:49 -0500 Message-ID: <52A9DE61.1090900@kamp.de> Date: Thu, 12 Dec 2013 17:03:45 +0100 From: Peter Lieven MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Occasional clockjump in Win2012 after Live Migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" , vrozenfe@redhat.com Hi, is anyone aware of a problem with a clock jump in Windows (observed in Server 2012) where after a successful live migration the clock jumps roughly 2 days into the future? Maybe this is already fixed we observed this with qemu-kvm-1.2.0. I have not yet managed to reproduce this, but it definetly happens. Where is Windows getting the system clock from? RTC or addtionally internal clocksources like HPET, PM_TIMER etc? Thanks, Peter