From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40349) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrSHo-00081r-DA for qemu-devel@nongnu.org; Fri, 13 Dec 2013 07:56:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VrSHc-0001vg-JH for qemu-devel@nongnu.org; Fri, 13 Dec 2013 07:56:08 -0500 Received: from mx.ipv6.kamp.de ([2a02:248:0:51::16]:59591 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VrSHc-0001v9-7R for qemu-devel@nongnu.org; Fri, 13 Dec 2013 07:55:56 -0500 Message-ID: <52AB03D8.2010505@kamp.de> Date: Fri, 13 Dec 2013 13:55:52 +0100 From: Peter Lieven MIME-Version: 1.0 References: <52A9DE61.1090900@kamp.de> <1148086635.36307665.1386907922045.JavaMail.root@redhat.com> <52AAC4E9.5010103@kamp.de> <1386929443.27116.2.camel@localhost> <52AAF46D.7090402@kamp.de> <1386939199.27116.32.camel@localhost> In-Reply-To: <1386939199.27116.32.camel@localhost> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Occasional clockjump in Win2012 after Live Migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vadim Rozenfeld Cc: qemu-devel@nongnu.org Am 13.12.2013 13:53, schrieb Vadim Rozenfeld: > On Fri, 2013-12-13 at 12:50 +0100, Peter Lieven wrote: >> Am 13.12.2013 11:10, schrieb Vadim Rozenfeld: >>> On Fri, 2013-12-13 at 09:27 +0100, Peter Lieven wrote: >>>> Am 13.12.2013 05:12, schrieb Vadim Rozenfeld: >>>>> Does your VM belong to domain or workgroup? >>>> We had 2 vServers where this happened. One was a Domain Controller and the second was an independent Workgroup Server. >>>> >>>> Do you have evidence how the DateTime Clock is driven in Windows 2012? >>> Should be CMOS periodic timer. >> you mean the RTC? > Right. >> Ok, so if there is a huge clock jump this one must have got messed up? > It might be. We have seen some similar problem during WHQL testing some > time ago. The problem happened because time on the host was not set > correct. So guest was taking this wrong time on boot and then it was a > big jump after resync with domain controller. our system forbids starting of vservers on a host where the time is not synched. ;-) the big jump i see seems to be introduced by the live migration. i will investigate further. Peter