/var/run/log/hostd.log of the affected ESXi host, you will observe an event indicating the vmx application has crashed, generating a core dump file:--> value = "/vmfs/volumes/<datstore-name>/<VM-Folder>/vmx-zdump.001" [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 4789 : An application (/bin/vmx) running on ESXi host has crashed (1 time(s) so far). An encrypted core file using keyId/vmfs/volumes/<datastore-name>/<vm-folder>/vmware.log of the affected virtual machine, you will observe a Panic state due to an unexpected signal (11) during the LWD unstun process: Cr(01) worker-###### #########-23-01-74-#### PANIC: Unexpected signal: 11. In(05) worker-###### #########-23-01-74-#### SymBacktrace[0] 000000d7299aa5c0 rip=000000d6e53705c0 in function Panic in object /bin/vmx loaded at 000000d6e50da000 [##############; [##############] SDM Data Mover: SDM Full Sync: The vCenter task failed: dp.vpx.fault.DiskClosing.summary [ [##############; [##############] SDM Data Mover: SDM Full Sync: The vCenter task for 'SDM Snapshot Sync Full' completed with state 'error'VMware by Broadcom engineering team is aware of this issue and fix is planned for a future ESXi release.