Failed to start the virtual machine
<YYYY-MM-DD>T<time> [261D2B70 info 'vm:/vmfs/volumes/Datastore/server/server.vmx'] Mounting VM complete.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VigorClientCnxDemux: VmdbCnx failed: Lost a connection to the running VMX instance.
--> Transport (VMDB) error -32: Pipe: Read failed.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VigorClientDisconnect: disconnect /vm/#2a81c0182271da01/ via /db/connection/#43/
<YYYY-MM-DD>T<time> [261D2B70 info 'vm:/vmfs/volumes/Datastore/server/server.vmx'] Unmounting VM begun.
<YYYY-MM-DD>T<time> [261D2B70 verbose 'Vmsvc.vm:/vmfs/volumes/Datastore/server/server.vmx'] Vigor client state callback 4 error Lost a connection to the running VMX instance.
--> Transport (VMDB) error -32: Pipe: Read failed.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VMDB unmount initiated for /vm/#2a81c0182271da01/.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VigorClientUnmountCb: Mount state values have changed for /vm/#2a81c0182271da01/.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#43/'
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VigorClientUnmountCb: Unmount complete for /vm/#2a81c0182271da01/.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VigorClientUnmountCb unset Vigor path on vm unmount.
<YYYY-MM-DD>T<time> [261D2B70 info 'vm:/vmfs/volumes/Datastore/server/server.vmx'] Unmounting VM complete.
<YYYY-MM-DD>T<time> [261D2B70 info 'vm:/vmfs/volumes/Datastore/server/server.vmx'] Reloading config state.
<YYYY-MM-DD>T<time> [261D2B70 info 'Libs'] VMHS: Transitioned vmx/execState/val to poweredOff
<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>
VMware vSphere ESXi
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. See also Additional Information section to find the details of each option.
Alternatively, to disable HPET using the vSphere Client:
Note: A virtual HPET is introduced with Virtual Hardware version 8.