Compute vMotion failing with switchover error and the VM fails to resume on the source ESXi host

Products

• VMware vSphere ESXi

Issue/Introduction

• Host-Local Swap has been enabled on the ESXi hosts as per Using Swap Files with vSphere
• Compute vMotion fails with a switchover error in the GUI: The migration has exceeded the maximum switchover time of 135 second(s).
• The virtual machine becomes unresponsive, cannot be pinged or accessed using RDP/SSH or via console and cannot be powered on/off.
• The nvram file of the VM is locked by the destination ESXi host with the below log messages in the vmware.log of the VM on the source ESXi host:
  
  [YYYY-MM-DDTHH:MM:SS] In(05) vmx - Migrate: Attempting to continue running on the source.
[YYYY-MM-DDTHH:MM:SS] In(05) vmx - OBJLIB-FILEBE : FileBEOpen: can't open '<VM_NAME>.nvram' : Failed to lock the file (262146).
[YYYY-MM-DDTHH:MM:SS] In(05) vmx - NVRAMMGR:  NvmanReopen: Failed to reopen NVRAM: Failed to lock the file
[YYYY-MM-DDTHH:MM:SS] Wa(03) vmx - MigrateResumeVM: Failed to reopen nvram file.

 

Resolution

This issue is resolved in VMware ESXi 8.0 U3b . To download go to - Download Broadcom products and software

To workaround this issue change the Host-Local Swap configuration to the same directory as the virtual machine. For more information refer to Using Swap Files with vSphere