Powering on a virtual machine fails with the error: Cannot open configuration file path_to_vmx_file

Products

• VMware vSphere ESXi
• VMware vSphere ESXi 6.0
• VMware vSphere ESXi 7.0
• VMware vSphere ESXi 8.0

Issue/Introduction

Symptoms:

• Cannot power on a virtual machine
• Powering on a virtual machine fails
• You see the error:

Cannot open the configuration file Path-to-vmx-file.
Cannot open file "Path-to-vmx-file": Reason.

Or

Failed - An error occurred while opening configuration file "Path-to-vmx-file": Could not find the file.

 

• For example:
   
  • Cannot open the configuration file /vmfs/volumes/4c####96-73####7e-####-18########55/TMPSQL/TMPSQL.vmx.
    Cannot open file "/vmfs/volumes/4c####96-73####7e-####-18########55/TMPSQL/TMPSQL.vmx": 16 (Device or resource busy).
  • Cannot open the configuration file /vmfs/volumes/bc####c7-21####3a/Test_VM/Test_VM.vmx.
    Cannot open file "/vmfs/volumes/bc####c7-21####3a/Test_VM/Test_VM.vmx": 13 (Permission denied).

Environment

VMware vSphere ESXi 6.x

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

When a virtual machine is powered on, the virtual machine tries to open the configuration file (.vmx file). This issue occurs if the .vmx file cannot be opened.

Resolution

• The Device or resource busy error is reported if you attempt to power on a virtual machine that is already powered-on on another host. It may also be a transient problem with the storage on which the virtual machine is located.
  
  To resolve this issue, retry the power-on operation after some time.
  
  Note: In HA-enabled clusters, before attempting a manual power-on operation, ensure that the virtual machine is not powered on on any host in the cluster.
  
  If the issue persists, it may indicate a locked virtual machine configuration file. To troubleshoot issues due to locked virtual machine configuration file, see https://knowledge.broadcom.com/external/article/314365
   
• The Permission Denied error is usually observed 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:

• This article is updated regularly with other reasons that may cause this issue. Check this article for updates.
• If you see a different reason for the failure, open a support request with Broadcom Support