Thanks for the checking.
We have an optional property in Linux customization specification, when doing Linux VM customization, customer can choose True or False for the "hwClockUTC", see it in the API document: https://vdc-download.vmware.com/vmwb-repository/dcr-public/184bb3ba-6fa8-4574-a767-d0c96e2a38f4/ba9422ef-405c-47dd-8553-e11b619185b2/SDK/vsphere-ws/docs/ReferenceGuide/vim.vm.customization.LinuxPrep.html It's to " Specifies whether the hardware clock is in UTC or local time. True when the hardware clock is in UTC. False when the hardware clock is in local time. "
For "VMware guest customization", we have own customization engine or cloud-init to do the real setting in a Linux VM. In this case, only our own customization engine supports customizing hardware clock, cloud-init does NOT.
Thanks for the checking.
We have an optional property in Linux customization specification, when doing Linux VM customization, customer can choose True or False for the "hwClockUTC", see it in the API document: https:/ /vdc-download. vmware. com/vmwb- repository/ dcr-public/ 184bb3ba- 6fa8-4574- a767-d0c96e2a38 f4/ba9422ef- 405c-47dd- 8553-e11b619185 b2/SDK/ vsphere- ws/docs/ ReferenceGuide/ vim.vm. customization. LinuxPrep. html
It's to
"
Specifies whether the hardware clock is in UTC or local time.
True when the hardware clock is in UTC.
False when the hardware clock is in local time.
"
For "VMware guest customization", we have own customization engine or cloud-init to do the real setting in a Linux VM. In this case, only our own customization engine supports customizing hardware clock, cloud-init does NOT.