Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

vMotion fails at 74% with the error, “The VM failed to resume on the destination during early power on”. (59665)

Last Updated: 5/28/2023Categories: TroubleshootingTotal Views: 20784Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Symptoms

In the hostd.log you see messages similar to:

2018-10-20T23:21:53.072Z info hostd[A1BF1B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:1231231231231231-2233223322332233/12312345-cccc-bbbb-aaaa-123123451234/test-vm.vmx] Checking for all objects accessibility (VM's current state: VM_STATE_EMIGRATING, stable? false)
2018-10-20T23:21:53.072Z info hostd[A1BF1B70] [Originator@6876 sub=VmObjectStorageMonitor] Object UUID 12312345-cccc-bbbb-aaaa-123123451234 APD state: Healthy
2018-10-20T23:21:53.072Z info hostd[A1BF1B70] [Originator@6876 sub=VmObjectStorageMonitor] Object UUID 12989b58-2a11-87d5-65f5-246e963e7c20 APD state: Healthy
2018-10-20T23:21:53.073Z info hostd[A1BF1B70] [Originator@6876 sub=Vcsvc.VMotionSrc (5422550518507384986)] ResolveCb: VMX reports needsUnregister = false for migrateType MIGRATE_TYPE_VMOTION
2018-10-20T23:21:53.073Z info hostd[A1BF1B70] [Originator@6876 sub=Vcsvc.VMotionSrc (5422550518507384986)] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "msg.migrate.fail.dst",
-->          message = "The source detected that the destination failed to resume.",
-->       }
-->    ],
-->    reason = "The source detected that the destination failed to resume.",
-->    messageInfo = (vim.vm.Message) [
-->       (vim.vm.Message) {
-->          id = "msg.migrate.fail.dst",
-->          text = "The source detected that the destination failed to resume.",
-->       }
-->    ]
-->    msg = "The source detected that the destination failed to resume.
--> "
--> }
2018-10-20T23:21:53.076Z info hostd[A1BF1B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/vsan:1231231231231231-2233223322332233/12312345-cccc-bbbb-aaaa-123123451234/test-vm.vmx] State Transition (VM_STATE_EMIGRATING -> VM_STATE_ON)

In the vmkernel.log you see messages similar to:

2018-10-21T03:12:42.047Z cpu13:857334255)WARNING: Migrate: 5454: 5422550532447652106 S: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.
2018-10-21T03:24:06.563Z cpu17:420159321)WARNING: Migrate: 5454: 5422550533132847308 S: Migration considered a failure by the VMX.  It is most likely a timeout, but check the VMX log for the true error.
2018-10-21T03:26:49.173Z cpu28:946706621)WARNING: Migrate: 5454: 5422550533291405060 S: Migration considered a failure by the VMX.  It is most likely a timeout, but check the [root@sewvxrail2:/vmfs/volumes/vsan:1231231231231231-2233223322332233/12312345-cccc-bbbb-aaaa-123123451234]
In the vmware.log of test-vm VM you see messages similar to:

2018-10-21T01:51:50.472Z| vmx| I125: Msg_Post: Error
2018-10-21T01:51:50.472Z| vmx| I125: [msg.nvram.wback1] Could not create '/vmfs/volumes/vsan:1231231231231231-2233223322332233/12312345-cccc-bbbb-aaaa-123123451234/test-vm.nv
ram': Failed to lock the file
2018-10-21T01:51:50.472Z| vmx| I125: ----------------------------------------
2018-10-21T01:51:50.474Z| vmx| I125: Vigor_MessageRevoke: message 'msg.nvram.wback1' (seq 47059135) is revoked
2018-10-21T01:51:50.474Z| vmx| W115: NVRAMMGR: Failed to create default NVRAM file (test-vm.nvram)
2018-10-21T01:51:50.474Z| vmx| I125: Module Nvman power on failed.
2018-10-21T01:51:50.474Z| vmx| I125: VMX_PowerOn: ModuleTable_PowerOn = 0
2018-10-21T01:51:50.474Z| vmx| I125: MigrateSetStateFinished: type=2 new state=12
2018-10-21T01:51:50.474Z| vmx| I125: MigrateSetState: Transitioning from state 11 to 12.
2018-10-21T01:51:50.474Z| vmx| I125: Migrate: Caching migration error message list:
2018-10-21T01:51:50.474Z| vmx| I125: [msg.migrate.resume.fail] The VM failed to resume on the destination during early power on.
2018-10-21T01:51:50.474Z| vmx| I125: Msg_Post: Error
2018-10-21T01:51:50.474Z| vmx| I125: [msg.migrate.resume.fail] The VM failed to resume on the destination during early power on.
2018-10-21T01:51:50.474Z| vmx| I125: ----------------------------------------
2018-10-21T01:51:50.475Z| vmx| I125: Vigor_MessageRevoke: message 'msg.migrate.resume.fail' (seq 47059136) is revoked
2018-10-21T01:51:50.481Z| vmx| I125: ToolsISO: Selected Tools ISO 'windows.iso' for 'windows7srv-64' guest.
2018-10-21T01:51:50.483Z| vmx| I125: Tools: ToolsRunningStatus_Exit, delayedRequest is 0x0
2018-10-21T01:51:50.483Z| vmx| I125: VMXVmdb_SetToolsVersionStatus: status value set to 'ok', 'current', install possible
2018-10-21T01:51:50.483Z| vmx| I125: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do
2018-10-21T01:51:50.484Z| svga| I125: SVGA thread is alive
2018-10-21T01:51:50.484Z| svga| I125: SVGA thread is exiting
2018-10-21T01:51:50.484Z| vmx| I125: Destroying virtual dev for scsi0:0 vscsi=10775
2018-10-21T01:51:50.484Z| vmx| I125: VMMon_VSCSIStopVports: No such target on adapter
2018-10-21T01:51:50.484Z| mks| I125: MKS PowerOff
2018-10-21T01:51:50.484Z| mks| I125: MKS thread is exiting
2018-10-21T01:51:50.484Z| vmx| I125: Migrate: cleaning up migration state.

Cause

The vMotion failed due to nvram lock not being released. This happens due to the host not being able to release the lock on NVRAM - Capacity disk on which VM is running. It can be due to an older version of firmware on NVRAM or older controller driver firmware or both.

Workaround

Shutdown / Power off VM and then power on the VM to clear the nvram lock then vMotion should work fine.

If the above steps does not resolve the issue then you would need to refer the below KB to investigate if there is any other lock on virtual machines.

For more details, refer to KB Article Investigating virtual machine file locks on ESXi (10051)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

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 vSAN

Related Versions:

VMware vSAN 8.0.x

VMware vSAN 7.0.x

VMware vSAN 6.x

VMware vSAN 6.5.x

Take Our Survey

Support Assistant