Starting the VM fails with error: Could not start VMX: msg.vmk.status.VMK_ADDR_UNMAPPED

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Unable to power on the virtual machine.
• When attempting to power on, the following error may appear:
  
  Power On virtual machine
VM name
Could not start VMX: msg.vmk.status.VMK_ADDR_UNMAPPED
   
• In the /var/log/vmkernel.log file, you see the entries similar to:
  
  2017-02-28T14:05:58.032Z cpu21:966431)World: 14296: VC opID hostd-f71e maps to vmkernel opID 6f73d4ba
2017-02-28T14:05:58.036Z cpu21:966431)Vol3: 2612: Failed to get object 28 type 2 uuid ########-####-########5f4b FD 4 gen 1 :Address temporarily unmapped
2017-02-28T14:05:58.264Z cpu21:966431)Vol3: 2612: Failed to get object 28 type 2 uuid ########-####-########5f4b FD 4 gen 1 :Address temporarily unmapped
2017-02-28T14:05:58.298Z cpu33:34057 opID=6de1ba35)World: 14296: VC opID host-671:543-0 maps to vmkernel opID 6de1ba35
2017-02-28T14:05:58.298Z cpu33:34057 opID=6de1ba35)Config: 346: "SIOControlFlag2" = 1, Old Value: 0, (Status: 0x0)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

 

 

 

Environment

VMware vSphere ESXi 5.5
VMware vSphere ESXi 6.5
VMware vSphere ESXi 6.0

Cause

This issue occurs because the LUN gets shrunk from the storage array side.

Resolution

This is an expected behaviour because the LUN shrinking is not supported.

To resolve this issue, configure the existing swap file in different datastore if only the swap location is set to that datastore.