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

Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster (2150316)

  • 1 Ratings

Symptoms

When attempting to Storage vMotion (SvMotion) a virtual machine with more than 64GB memory from a datastore to a vSAN datastore, you experience these symptoms:
  • The SvMotion task fails with error messages similar to:

    Failed waiting for data. Error 195887105. Failure.
    vMotion migration [-1062686815:9116155795999752156] failed: remote host <Destination ESXi host IP> failed with status Failure.
    vMotion migration [-1062686815:9116155795999752156] remotecall returned Failure
    Migration to host <Destination ESXi host IP> failed with error Failure (195887105).
    File system specific implementation of LookupAndOpen[file] failed
    File system specific implementation of LookupAndOpen[file] failed
    Failed to extend swap file from 0 KB to 134217728 KB.
    Current swap file size is 0 KB.
    vMotion migration [-1062686815:9116155795999752156] failed to initialize a valid destination swapfile: Failure.



  • In the vmware.log file for the virtual machine, you see entries similar to:

    2017-04-20T02:36:27.090Z| vcpu-0| I120: [msg.checkpoint.precopyfailure] Migration to host <Destination ESXi host IP> failed with error Failure (0xbad0001).
    2017-04-20T02:36:27.090Z| vcpu-0| I120: [vob.vmotion.resolve.swap.type.remotecall.failed] vMotion migration [c0a8afa1:9116155837453402292] remotecall returned Failure
    2017-04-20T02:36:27.090Z| vcpu-0| I120: [vob.vmotion.net.inval.msg.status] vMotion migration [c0a8afa1:9116155837453402292] failed: remote host <Destination ESXi host IP> failed with status Failure.


  • In the /var/log/vmkernel.log file on the SvMotion destination host:

    2017-04-20T02:36:26.876Z cpu70:9407046)swapobj: SwapObjDumpVmklinkResponse:1495: {ID:0x260; type:GET_OBJECT_ID; ret:{status:bad0001; open:{lock:s/volumes/vsan:52981dacd61373ab-4989ed85301acb21/a61ef858-cabc-8fa4-8a77-1402ec84e520/test-vm.vswp; $
    2017-04-20T02:36:26.876Z cpu70:9407046)swapobj: SwapObjGetObjectID:1020: Error returned from vmklink call: Failure
    2017-04-20T02:36:26.954Z cpu16:9407028)WARNING: VSAN: VsanIoctlCtrlNode:2068: aa1ef858-ee6e-a303-1831-1402ec84e520: RPC to DOM returned: Not supported
    2017-04-20T02:36:26.954Z cpu70:9407046)swapobj: SwapObjDumpVmklinkResponse:1495: {ID:0x264; type:SETATTR; ret:{status:bad0001; open:{lock:s/volumes/vsan:52981dacd61373ab-4989ed85301acb21/a61ef858-cabc-8fa4-8a77-1402ec84e520/test-vm.vswp; dev:}}}
    2017-04-20T02:36:26.954Z cpu70:9407046)swapobj: SwapObjSetAttr:842: Error returned from vmklink call: Failure
    2017-04-20T02:36:26.954Z cpu70:9407046)WARNING: SwapExtend: 694: Failed to extend swap file from 0 KB to 134217728 KB.
    2017-04-20T02:36:26.954Z cpu70:9407046)WARNING: SwapExtend: 697: Current swap file size is 0 KB.
    2017-04-20T02:36:26.954Z cpu70:9407046)WARNING: SwapExtend: vm 9407025: 705: Failed to extend swap file. type=regular from 0 KB to 134217728 KB. currently 0. status=Failure
    2017-04-20T02:36:27.076Z cpu70:9407046)WARNING: VMotionRecv: 1839: 9116155837453402292 D: failed to initialize a valid destination swapfile: Failure.

Cause

It occurs as the swap file cannot be created on the vSAN datastore, as the size of the file exceeds the default limit for storage vMotion operations.

Note: This issue affects only storage vMotion or XvMotion operations.

Resolution

This is a known issue affecting vSAN 6.5, currently there is no resolution. 

To work around the issue, apply one of these options:
  • Set an advanced parameter on the destination ESXi host to increase the maximum memory allowed for the swap file.

    To increase the swap file maximum size, run this command on the destination ESXi host:

    # esxcfg-advcfg -s 0 /Mem/SwapExtendChunkSizeInMB

    Note: Reboot is not required.

    To reset it back to the default value after the SvMotion completes:

    # esxcfg-advcfg -s 65536 /Mem/SwapExtendChunkSizeInMB
  • Do a cold storage migration instead of an SvMotion.

    Note
    : This requires the virtual machine to be powered off.

Additional Information

For information about the location of virtual machine log files (vmware.log), see Locating virtual machine log files on an ESXi/ESX host (1007805).

See Also

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.

Feedback

  • 1 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.
  • 1 Ratings
Actions
KB: