YYYY-MM-DDTHH:MM:SS In(05) ####-# - FILE: Open error on /vmfs/volumes/########-########-####-############/VM_NAME/VM_NAME.vmx~: Resource temporarily unavailableYYYY-MM-DDTHH:MM:SS In(05) ####-# - FILEIO: AtomicTempFile: Failed to create temporary file, Error (2), errno: 11YYYY-MM-DDTHH:MM:SS In(05) ####-# - Msg_Reset:YYYY-MM-DDTHH:MM:SS In(05) ####-# - [msg.configdb.failcreatetemp] An error occurred while creating temporary file for /vmfs/volumes/########-########-####-############/VM_NAME/VM_NAME.vmxYYYY-MM-DDTHH:MM:SS In(05) ####-# - [msg.configdb.failcreatetemp] An error occurred while creating temporary file for /vmfs/volumes/########-########-####-############/VM_NAME/VM_NAME.vmxYYYY-MM-DDTHH:MM:SS In(05) ####-# - SNAPSHOT: SnapshotConfigWrite: Failed to write config file "/vmfs/volumes/########-########-####-############/VM_NAME/VM_NAME.vmx".YYYY-MM-DDTHH:MM:SS In(05) ####-# - PANIC: Critical snapshot error.YYYY-MM-DDTHH:MM:SS In(05) ####-# - Backtrace:...
vCSA:8.0.x
ESX: 8.0.x, 8.0 Update 3g
The hypervisor cannot create the required temporary configuration file (.vmx~) because of stale metadata entries, locks on the VMFS datastore or VMFS metadata corruption .
Option 1: Storage vMotion the virtual machine.
Option 2: Recreate the VMX file as per Rebuilding the virtual machine's .vmx file from vmware.log)
Option 3: Create a new VM with no disks and add the existing disks to the new VM.
Contact Broadcom Support for further assistance if needed.
Collecting diagnostic information for VMware ESXi using vSphere Client