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

My Subscriptions

Loading

Knowledge Base

vMotion fails with the error: Error bad003F (1036834)

Last Updated: 3/2/2016Categories: TroubleshootingTotal Views: 28270Language:
JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

If you move some new ESX/ESXi 4.1 Update 1 hosts into an existing cluster with ESX/ESXi 4.0 Update 2 hosts, migrating virtual machines onto the new host using vMotion fails.

If you move some new ESXi 5.x hosts into an existing cluster with ESXi 5.x hosts, migrating virtual machines onto the new host using vMotion fails.

vMotion fails between 9% and 28%.

This issue occurs even when the vMotion network is set up correctly and vmkping between the hosts is successful.

Issue may also occur for Storage vMotion.

The virtual machine's vmware.log contains entries similar to:

Mar 29 08:55:35.764: vmx| VMXAIOMGR: Using: simple=Generic unbuf=Generic
Mar 29 08:55:35.778: vmx| MigratePlatformInitMigration: DiskOp file set to /vmfs/volumes/datastore/virtual_machine/virtual_machine.tmp
Mar 29 08:55:35.785: vmx| MigrateWaitForData: waiting for data.
Mar 29 08:55:35.786: vmx| MigrateSetState: Transitioning from state 7 to 8.
Mar 29 08:56:55.360: vmx| MigrateSetStateFinished: type=2 new state=11
Mar 29 08:56:55.361: vmx| MigrateSetState: Transitioning from state 8 to 11.
Mar 29 08:56:55.362: vmx| Migrate_SetFailure: Failed waiting for data. Error bad003f. Connection closed by remote host, possibly due to timeout.
Mar 29 08:56:55.362: vmx|
Mar 29 08:56:55.363: vmx| Migrate: cleaning up migration state.
Mar 29 08:56:55.363: vmx| MigrateSetState: Transitioning from state 11 to 0.
Mar 29 08:56:55.364: vmx| Msg_Post: Error
Mar 29 08:56:55.364: vmx| [vob.migrate.net.xfer.recvfailed.status] The migration transfer failed during the receive operation to socket 4100A43A7510: received 0/72 bytes: Timeout
Mar 29 08:56:55.364b: vmx| [msg.moduletable.powerOnFailed] Module Migrate power on failed.
Mar 29 08:56:55.365: vmx| ----------------------------------------
Mar 29 08:56:55.372: vmx| VMX_PowerOn: ModuleTable_PowerOn = 0
Mar 29 08:56:55.429: vmx| WORKER: asyncOps=0 maxActiveOps=0 maxPending=0 maxCompleted=0
Mar 29 08:56:56.460: vmx| Vix: [104976 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
Mar 29 08:56:56.466: vmx| Vix: [104976 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0
Mar 29 08:56:56.467: vmx| Transitioned vmx/execState/val to poweredOff
Mar 29 08:56:56.467: vmx| Vix: [104976 mainDispatch.c:3571]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0
Mar 29 08:56:56.468: vmx| Vix: [104976 mainDispatch.c:3597]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
Mar 29 08:56:56.468: vmx| VMX idle exit
Mar 29 08:56:56.469: vmx| VMIOP: Exit
Mar 29 08:56:56.470: vmx| Vix: [104976 mainDispatch.c:652]: VMAutomation_LateShutdown()
Mar 29 08:56:56.471: vmx| Vix: [104976 mainDispatch.c:602]: VMAutomationCloseListenerSocket. Closing listener socket.
Mar 29 08:56:56.478: vmx| Flushing VMX VMDB connections
Mar 29 08:56:56.479: vmx| VmdbPipeStreamsOvlError: write failed, draining reads
Mar 29 08:56:56.479: vmx| VmdbPipeStreamsOvlError: Couldn't initiate write
Mar 29 08:56:56.482: vmx| VMX exit (0).
Mar 29 08:56:56.482: vmx| VMX has left the building: 0.

Resolution

To resolve this issue, isolate the vMotion traffic by creating a separate vMotion network.

Related Information

For related information, see Diagnosing VMware vMotion failure at 10% (1003734).
Understanding and troubleshooting vMotion
vMotion が次のエラーで失敗する：Error bad003F

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

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 vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.0.x Installable

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant