When executing incremental snapshot tasks (creation, deletion, or consolidation), the following symptoms occur:
/var/vmfs/<Datastore_UUID>/<Virtual_Machine_Directory>/vmware.log: ####-##-##T##:##:## In(05) vcpu-0 [msg.poweroff.commitOn] Performing disk cleanup. Cannot power off. ####-##-##T##:##:## In(05) vcpu-0 [msg.disklib.lockinfo.local] Locking conflict for file "/vmfs/volumes/########/####/####.vmdk"/var/run/log/hostd.log on ESXi host:An operation required the virtual machine to quiesce and the virtual machine was unable to continue running.VMware ESXi 8.x
VMware vCenter Server 8.x
This issue is caused by resource contention and file lock conflicts resulting from the simultaneous execution of a third-party backup job and a separate incremental snapshot/consolidation task on the same virtual machine.
When both operations attempt to manipulate the VMDK file chain at the same time:
The backup software opens a session via NFC to read the snapshot disk (00000#.vmdk).
Simultaneously, vSphere attempts to complete a snapshot consolidation, which requires merging delta disks and unstunning the VM.
Because the backup process is still interacting with the file chain, ESXi encounters a Locking conflict.
To prevent severe disk corruption or data inconsistency, the ESXi hypervisor intentionally terminates (powers off) the VCPU threads.