Search the VMware Knowledge Base (KB)
View by Article ID

Powering on virtual machines in VMware vSAN 5.5 fails with error: Failed to create swap file (2097906)

  • 12 Ratings


  • Cannot power on virtual machines residing in VMware vSAN5.5
  • Powering on virtual machines in vSAN 5.5 fails
  • You see the error:

    Failed to create swap file

  • In the /var/log/vmkernel.log file on ESXi host, you see entries similar to:

<YYYY-MM-DD>T<TIME>.708Z cpu9:12823401)WARNING: VSAN: VsanIoctlCtrlNode:1624: 65116a53-f9a2-5c78-b9e8-c80aa988185c: RPC to DOM returned: Out of memory
<YYYY-MM-DD>T<TIME>.884Z cpu14:12823397)swapobj: SwapObjDumpVmklinkResponse:1236: {ID:0x211; type:CREATE; ret:{status:bad0001; open:{lock:s/volumes/vsan:52a52ed80c06c1b4-303a69b14df03e25/cecd3a53-7a99-b7c6-6b09-c80aa9881754/vmname.vswp
<YYYY-MM-DD>T<TIME>.884Z cpu14:12823397)swapobj: SwapObjCreate:527: Error returned from vmklink call: Failure
<YYYY-MM-DD>T<TIME>.884Z cpu14:12823397)WARNING: Swap: 3751: Failed to create swap file '/vmfs/volumes/vsan:52a52ed80c06c1b4-303a69b14df03e25/cecd3a53-7a99-b7c6-6b09-c80aa9881754/vmname.vswp' : Failure
<YYYY-MM-DD>T<TIME>.884Z cpu14:12823397)WARNING: Swap: vm 12823400: 4406: Swap initialization failed Failure
<YYYY-MM-DD>T<TIME>.130Z cpu15:34773)World: 14296: VC opID hostd-13b1 maps to vmkernel opID daeb8bcc
<YYYY-MM-DD>T<TIME>.352Z cpu10:34297)Config: 346: "SIOControlFlag2" = 4, Old Value: 5, (Status: 0x0)
<YYYY-MM-DD>T<TIME>.003Z cpu1:34294)World: 14296: VC opID hostd-baa6 maps to vmkernel opID 49863fe9


This issue is resolved in VMware ESXi 5.5 Patch Release ESXi550-201502001 (Build 2456374), available at VMware downloads.

If you are unable to upgrade to VMware ESXi 5.5 Patch Release ESXi550-201502001 (Build 2456374), work around this issue by restarting the Cluster Level Object Manager (CLOM) service.
To restart the Cluster Level Object Manager (CLOM) service:
  1. Log in as root to the ESXi host through SSH.
  2. Run this command:

    /etc/init.d/clomd restart

Note: Restarting the clomd service briefly interrupts CLOM operations. The length of the outage should be less than one second. However, if a virtual machine is being provisioned at the time the clomd service is restarted, that provisioning task may fail.

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

05/06/2015 - Added the details of ESXi 5.5 patch to the resolution

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 12 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 12 Ratings