Powering on a virtual machine fails with the error: Could not create '/vmfs/volumes///.nvram':

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Cannot power on a virtual machine
• Powering on a virtual machine fails
• You see the error:
  
  Could not create '/vmfs/volumes/Datastore_Name/VM_name/VM_Name.nvram': Reason
  
  where Reason can be any one of these:
   
  • Failed to lock the file
  • Could not find the file
    
    
• Error: [msg.nvram.wback1] Could not create '/vmfs/volumes/########-####-########beb4/vm/vm.nvram': Failed to lock the file
• Sample log snippet in vmware.log:
  
  [YYYY-MM-DDTHH:MM:SS]| Worker#1| I120: ToolsVersion: Status is supported old because this is status of monolithic version, and vsock_win2k3 and 78 more components are missing from the guest.
[YYYY-MM-DDTHH:MM:SS]| Worker#1| I120: ToolsVersionGetStatusWorkerThread: Tools status 2 derived from environment
[YYYY-MM-DDTHH:MM:SS]| vmx| W110: NVRAMMGR: No valid NVRAM file found, will create default NVRAM.
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: Msg_Post: Error
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: [msg.nvram.wback1] Could not create '/vmfs/volumes/########-####-########beb4/vm/vm.nvram': Failed to lock the file
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: ----------------------------------------
[YYYY-MM-DDTHH:MM:SS]| vmx| W110: NVRAMMGR: Failed to create default NVRAM file (vm.nvram)
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: Module Nvman power on failed.
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: VMXVmdb_SetToolsVersionStatus: status value set to 'oldTools', 'supportedOld', install possible
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: VMXVmdb_SetToolsVersionStatus: status value set to 'oldTools', 'supportedOld', install possible
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do
[YYYY-MM-DDTHH:MM:SS]| svga| I120: SVGA thread is exiting
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: Destroying virtual dev for scsi0:0 vscsi=8235
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: Destroying virtual dev for scsi0:1 vscsi=8236
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: Destroying virtual dev for scsi0:2 vscsi=8237
[YYYY-MM-DDTHH:MM:SS]| vmx| I120: VMMon_VSCSIStopVports: No such target on adapter

Cause

The NVRAM file of a virtual machine stores the state of BIOS settings of the virtual machine. When a virtual machine is powered on, the contents in the NVRAM file are read to emulate the BIOS of the virtual machine. If for any reason the NVRAM file could not be opened, you see this error. There are multiple reason for a failure while opening a NVRAM file.

Resolution

Error 1: Failed to lock the file

This issue occurs if another process/host has already opened the virtual machine's NVRAM file that your process/host
is attempting to open.

To resolve this issue, ensure that the file is available for use by the host/process. For more information, see Investigating virtual machine file locks on ESXi hosts

Error 2: Could not find the file

This issue occurs if the NVRAM file mentioned in the virtual machines configuration file(*.vmx) is not available anymore.

To work around this issue:

1. Edit the virtual machine's configuration file. For more information see, Tips for editing a .vmx file (1714).
2. Remove this line referring to NVRAM file:
   
   nvram = "file_name"
   sample line from vmx. : nvram = "vm.nvram"
   
   
3. Power on the virtual machine.

Note: 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 VMware Support. For more information, see Filing a Support Request in Customer Connect (2006985).

Workaround:
Rather then rebooting the Source Host; edit the vmx file of the locked VM & remove the entry: nvram = "file_name"