Hello,
I'm running Windows 2003 Standard virtual machines under a Windows 2008 Datacenter Hyper-V Server. The system time of all of my virtual machines is 3 hours later than the time of my physical host.
When I try to change the time on my VMs, it resets itself back to the wrong time after a few seconds, and I get this message in the System log:
Event Type: Information
Event Source: W32Time
Event Category: None
Event ID: 35
Description:
The time service is now synchronizing the system time with the time source VM IC Time Synchronization Provider.
Any ideas on what might be causing this?
Thanks,
Stephen
Are any of your DCs on physical boxes? If they are then set them up to pull time from pool.ntp.org. Then set up your hosts and guests to pull from that DC. Allow firewall exceptions for NTP inbound on that DC.
If all DCs are VMs then set up one of the physical hosts to poll pool.ntp.org for time and then set the VMs to poll the host. Again set the firewall accordingly.
http://blog.mpecsinc.ca/2011/01/hyper-v-preparing-high-load-vm-for-time.html
We have had a lot of pain over the time skew situation for VMs.
The above methods work for us. In some cases we drop in an HP MicroServer with Win2K8 R2 running as a DC and set it up to poll pool.ntp.org and then have all VMs poll it for time.
The problem has to do with the polling frequency needed as indicated in the blog post. Do that to ntp.org's servers and they will pass along the Kiss-Of-Death packets basically killing the ability to poll their servers for time.