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

vMotion from ESXi 4.1/5.0/5.1GA to ESXi 5.1 fails with the error: Failed to resume destination VM: Not found (2036892)

  • 7 Ratings

Symptoms

  • Cannot perform a vMotion from an ESXi 4.1/5.0/5.1 GA host to an ESXi 5.1 host
  • Performing a vMotion from ESXi 4.1/5.0 to ESXi 5.1 fails at 65%
  • You see the error:

    Failed to resume destination VM: Not found.
    vMotion migration [168428389:1349422130230437] could not find destination swapfile. Verify matching source and destination host swap settings, including matching VM or swapfile path UUIDs, and storage accessibility.


  • In the hostd.log file of the destination, you see entries similar to:

    [7E358B90 verbose 'VMotionDst (1349422130230437)' opID=144E93E1-0000062D-b0-99-29] Migration changed state from BEGIN to MIGRATING
    [7E317B90 verbose 'vm:/vmfs/volumes/505c3190-b80d5c00-c79b-005056014028/svgw2k303/svgw2k303.vmx'] VMotionCmdCb [1349422130230437] 'from': done
    [7DC40B90 verbose 'vm:/vmfs/volumes/505c3190-b80d5c00-c79b-005056014028/svgw2k303/svgw2k303.vmx'] Handling message _vmx1: vMotion migration [a0a0365:1349422130230437] could not find destination swapfile. Verify matching source and destination host swap settings, including matching VM or swapfile path UUIDs, and storage accessibility.
    [7E040B90 info 'VMotionDst (1349422130230437)'] ResolveCb: VMX reports needsUnregister = true for migrateType MIGRATE_TYPE_VMOTION
    [7E040B90 info 'VMotionDst (1349422130230437)'] ResolveCb: Failed with fault: (vmodl.fault.SystemError) {
    -->                value = "1349422130230437",
    -->          message = "vMotion migration [a0a0365:1349422130230437] could not find destination swapfile.  Verify matching source and destination host swap settings, including matching VM or swapfile path UUIDs, and storage accessibility.
    [7E040B90 verbose 'VMotionDst (1349422130230437)'] Migration changed state from MIGRATING to UNREGISTERING
    [7E040B90 verbose 'VMotionDst (1349422130230437)'] Finish called
    [7E040B90 verbose 'VMotionDst (1349422130230437)'] Migration changed state from UNREGISTERING to DONE


  • This issue may occur with all virtual machines on the source host or only with some virtual machines
  • In the VMkernel log on the source host, you may see a message similar to:

    vm21 vmkernel: 57:00:17:41.145 cpu9:14775)WARNING: Migrate: 296: 1353591361566805 S: Failed: Failed to resume VM (0xbad0044) @0x418000ce26c0

    or

    vm21 vmkernel: 57:00:17:41.207 cpu1:14646)WARNING: Migrate: 4343: 1353591361566805 S: Migration considered a failure by the VMX. It is most likely a timeout, but check the VMX log for the true error.

Resolution

This issue has been resolved in ESXi 5.1 Patch 01.


To work around this issue, use one of these two options:

Additional Information

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

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

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