Quick description so that people will not give me completely useless pointers like google has been doing.
1 - big hairy servers. 2008 r2 data centre, hyper-v with clustering, 5 active VMs per server with about 32gb each. Guests are all 2008 r2.
2 - trouble has a 10g tomcat and is the only one drifting.
3 - There appears no way to tell the guest vm "you really REALLY want VM IC Time Synchronisation" like all the other VMs.
4 - NONE of these vms is a DC, that duty belongs to a completely separate machine. Repeat, the VM's are stand alone w2k8 r2, they areNOT in a domain.
5 - *EVERYONE* except this one VM is happy. Hosts getting time from the PDC, PDC getting it from NTP.
6 - Rebooting anything is an ABSOLUTE LAST RESORT. This is not the dark ages anymore.
7 - Integration stuff includes time stuff. Windows Time Service appears to be running as "delayed start"
8 - I don't need NTP accuracy, I just want VM IC Time Synchronisation to *work* 1~2 seconds is fine.
...
On this and only this vm, w32tm /query /source says
Local CMOS Clock.
The clock drifts back about 5 seconds in between 45 and 70 minutes. When first noticed, the windows time service was mysteriously "disabled" and this drifting started at 4am on a sunday when no one was playing with it. Before that it appears to
have been in sync for some time.
CPU for this guest is all over the place, typically around 25% (the host registers a whole 1% cpu) the java process is quite busy brewing logfiles like there is no tomorrow. Possibly related to this, the terminal window's cmd.exe is horribly laggy.
Experimentally restarting windows time has no effect, it is stuck on Local CMOS Clock,
The only interesting thing is that in the registry, there is no "IPC" under "VMICTimeProvider". I do not know where it went.
Q1 - what pokes it when it gets 5 seconds behind, how does it poke it.
Q2 - where did VM IC Time Synchronizaition Client go, why doesn't it come back?
So, any ideas, pointers or actually useful pages?
=^x^=