From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39799)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1VrSFQ-0006Ak-5o
	for qemu-devel@nongnu.org; Fri, 13 Dec 2013 07:53:46 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1VrSFK-0001LW-6b
	for qemu-devel@nongnu.org; Fri, 13 Dec 2013 07:53:40 -0500
Received: from mx1.redhat.com ([209.132.183.28]:7453)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1VrSFJ-0001LJ-Ue
	for qemu-devel@nongnu.org; Fri, 13 Dec 2013 07:53:34 -0500
Message-ID: <1386939199.27116.32.camel@localhost>
From: Vadim Rozenfeld <vrozenfe@redhat.com>
Date: Fri, 13 Dec 2013 23:53:19 +1100
In-Reply-To: <52AAF46D.7090402@kamp.de>
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>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Occasional clockjump in Win2012 after Live
	Migration
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Lieven <pl@kamp.de>
Cc: qemu-devel@nongnu.org

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.

best regards,
Vadim.   
> 
> Peter
>