Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

vMotion fails at 82% with the hostd log error: "Source detected that destination failed to resume" (1006052)

Last Updated: 3/21/2024Categories: TroubleshootingTotal Views: 77896Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

vMotion fails at 82%

Cannot migrate a virtual machine with vMotion

In the /var/log/vmware/hostd.log file on source ESX host, you see the error:

ResolveCb: Failed with fault: (vmodl.fault.SystemError) {
reason = "Source detected that destination failed to resume."
msg = ""
}

In the /var/log/vmware/hostd.log file, you see the entry:

Upgrade is required since hwVersion in config file is 3

Cause

This issue occurs due to incorrect datastore information or out-of-date virtual hardware.

Note: A similar issue is seen when there is a misconfiguration of the swap file locations between the ESXi/ESX host and vCenter Server. For more information on configuring swap files, see Storing a virtual machine swap file in a location other than the default in ESX/ESXi (1004082).

Resolution

Incorrect datastore information

To determine if this issue is caused by incorrect datastore information, run this command on your ESX hosts:

# vdf -h

You see output similar to:

[root@esx01 ~]# vdf -h
/vmfs/volumes/1dd794c6-cc279de7
600G 438G 161G 73% /vmfs/volumes/VM_STOR2
/vmfs/volumes/e2978cef-5a532852
400G 282G 117G 70% /vmfs/volumes/VM_STOR7

[root@esx02 ~]# vdf -h
/vmfs/volumes/1dd794c6-cc279de7
600G 438G 161G 73% /vmfs/volumes/VM_STOR2
/vmfs/volumes/e2978cef-5a532852
400G 282G 117G 70% /vmfs/volumes/VM_STOR7

[root@esx03 ~]# vdf -h
/vmfs/volumes/36132c1c-6f72083e
600G 437G 162G 72% /vmfs/volumes/VM_STOR2
/vmfs/volumes/e01dc51c-0e591900
400G 282G 117G 70% /vmfs/volumes/VM_STOR7

In this example, the third host identifies the datastore with a different UUID. Adding a host by these four different methods produces four different UUIDs:

hostname

hostname.domainname

IP.address.of.host

HOSTNAME vs. hostname

Run this command to find which methods were used to mount the datastores, SSH into each host:

# esxcfg-nas -l

To resolve this issue:

If the virtual machine(s) that are attached to the datastore(s) in question can be powered off:

Power off the virtual machine(s).

Unmount the NFS datastore.

Mount the NFS datastore with the required details to be consistent with all the hosts that have access to this datastore (that is, HOSTNAME, hostname, hostname.domainname, or IP.address.of.host).

Power on the virtual machine(s).

If the virtual machine(s) cannot be powered off:

Use Storage vMotion to move virtual machines to a volume that is equally shared by the hosts. For more information, see Moving virtual machines with Storage vMotion (1005544).

Unmount the NFS datastore.

Mount the NFS datastore with the required details to be consistent with all the hosts that have access to this datastore (that is, HOSTNAME, hostname, hostname.domainname, or IP.address.of.host).

Move the virtual machine(s) back to the datastore(s) using Storage vMotion.

Note: This procedure is applicable for NFS datastores, with block storage (local, Fiber Channel, iSCSI) steps 2 and 3 can be replaced with unpresenting/re-presenting the LUN from the ESX/ESXi host. For more information, see Removing a LUN containing a datastore from VMware ESXi/ESX 4.x (1029786)

If the issue persists:

Unmap and remap the LUN from the storage side.

Confirm that the UUID displays correctly, both from an SSH Client and in the datastore of the host.

In the var/log/vmkwarning file, look for an entry similar to:

Failed to migrate vswp file" with /vmfs/ incorrect_datastore_ID

If you see this entry, power off the virtual machine.

Right-click the virtual machine in the Inventory and choose Edit Settings.

Click the Option tab.

Select a swap file location.

Select Always store with the virtual machine.

Out-of-date virtual hardware

To determine if this issue is caused by out-of-date hardware, in the /var/log/vmware/hostd.log file look for an entry similar to:

Upgrade is required since hwVersion in config file is 3

This log entry indicates that the virtual machine's virtual hardware is at an earlier version than is required.

To confirm that the virtual hardware is out-of-date:

Right-click on the virtual machine in the Inventory and choose Edit Settings.

Check in the upper right corner of the Virtual Machine Properties screen. If the version is less than 4, you must upgrade the virtual hardware for this virtual machine.

Related Information

Storing a virtual machine swap file in a location other than the default in ESX/ESXi
Moving virtual machines with Storage vMotion
Removing a LUN containing a datastore from VMware ESXi/ESX 4.0 and 4.1
vMotion が 82% で次の hostd ログ エラーで失敗する： Source detected that destination failed to resume.
vMotion 在完成 82% 时失败并显示 hostd 日志错误：源检测到目标无法恢复。

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant