Lock was not free
To prevent concurrent changes to critical virtual machine files, ESX hosts establish exclusive locks on these files when the virtual machine is powered on. In some cases, these virtual machine files remain locked even when the virtual machine is powered off. These files cannot be accessed by other ESX hosts while locked and the virtual machine fails to to power-on on those hosts.
To resolve this issue, see
Investigating virtual machine file locks in ESX/ESXi (10051).
Invalid metadata
A virtual machine fails to power on with this error if the metadata region of the VMFS datastore used for the heartbeat protocol is incorrect for some reason.
No Connection
This error is reported if the ESX host loses access to the datastore on which the swap file is created. The most common reasons are intermittent SAN and network issues, such as unreachable storage or high latencies.
To resolve this issue, ensure that there are no issues with the storage or network in your environment.
For related information, see:
Permission Denied
This error is usually seen while powering on virtual machines located on NFS datastores. This issue may occur due to permissions issues on the NFS datastore.
To resolve this issue, ensure that the host has the correct read/write permissions to access the NFS export.
If your storage array has the No Root Squash option, ensure that the option is enabled or contact your Storage Administrator.
Notes: