After vMotion some guests went 2 hours ahead in time.
2 hours ahead of UTC is exactly our timezone.
Why would it do that? AFAICS both source and destination hosts have the same configuration.
But apparently not. What could be wrong?
VMware ESXi – Fix Wrong Time After vMotion
time-synchronizationvmotionvmware-esxi
Related Topic
- How to crack the 1 Gbit iSCSI limit between ESXi and VNXe
- VMware Vmotion 5.1 fails at 51% , Between two identical new vmware servers
- Monitor VMware 5.5 ESXi Storage vMotion Performance
- VMware ESXi – Protecting Root Account from Lockout
- Windows – Find windows process that is changing time back 1 hour
- Kubernetes – Synchronizing Date and Time in Pods Hosted in Own Datacenter
Best Answer
Check your hosts' hardware clocks in the BIOS...
This is a common issue, so I set the hardware clock to UTC on my systems or have the OS update the hardware clock once synced with NTP in the build process.