Failed to start the virtual machine
<YYYY-MM-DD>T<time> [27480B70 info 'Vmsvc.vm:/vmfs/volumes/Datastore/server/server.vmx'] Upgrade is required for virtual machine, version: 4
<YYYY-MM-DD>T<time> [261D2B70 verbose 'Vmsvc.vm:/vmfs/volumes/Datastore/server/server.vmx'] Vigor client state callback 0 error Lost a connection to the running VMX instance.
--> Transport (VMDB) error -32: Pipe: Read failed.
<YYYY-MM-DD>T<time> [261D2B70 verbose 'Vmsvc.vm:/vmfs/volumes/Datastore/server/server.vmx'] Power On translated error to vim.fault.GenericVmConfigFault
<YYYY-MM-DD>T<time> [261D2B70 info 'Vmsvc.vm:/vmfs/volumes/Datastore/server/server.vmx'] Power On failed: vim.fault.GenericVmConfigFault
<YYYY-MM-DD>T<time> [261D2B70 verbose 'Vmsvc.vm:/vmfs/volumes/Datastore/server/server.vmx'] Power On message: Failed to start the virtual machine.</time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time>
<YYYY-MM-DD>T<time> | vmx| I120: ExtCfgDevice: HPET cannot work without extended configuration device.</time>
"The device "hpet0" is not supported by the current hardware version"
VMware vSphere ESXi 6.5.x
VMware vSphere ESXi 6.7.x
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
This issue occurs when high precision event timer (HPET) is enabled in VM hardware versions 7 and below.
To resolve this issue, perform one of the below options.
Note: Virtual HPET is introduced with Virtual Hardware version 8.