We've been battling with VM Time issues mainly on Win 2012R2 Server where time of a VM thats been powered off and restarted is set to GMT time even though TZ etc are correct on hardware, VM and hypervisor machine.
I found this KB https://portal.nutanix.com/#/page/kbs/details?targetId=kA03200000098c9CAA that relates to the problem however I'd consider this a workaround in the short term and to me is not a solution wehre I haev to set a registry item to fix the time issue.
When I logged a support case for this I got refered to the KB article.
Is the problem going to be resolved as a permant fix in any up coming releases?
Can someone explain to me what the actual technical problem is and why VM can't get the correct time from the underlyind hypervisor?
Best answer by Chandru
The default timezone is UTC when a user vm is created. We cannot set the time zone to the AHV hosts time zone because the linux VM's will expect the time provided by AHV to be in UTC. If we set the hwclock to your local time zone as default for all the vm's, then linux vm's will come up with a wrong time same as Windows does with UTC. There is an enhancement work in progress to identify the OS type and feed the correct timezone accordingly but for now setting hwclock_timezone or editing the registry is the option for Windows vm's.