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
