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 at 10% with the error: A general system error occurred: Migration failed while copying data, Broken Pipe (1013150)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 99314Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

vMotion fails at 10%

You see these errors in vCenter Server:

A general system error occurred: Migration failed while copying data, Broken Pipe
Migration failed while copying data. Connection reset by peer

A general system error occured: Failed to start migration pre-copy Error 0xbad010d. The Esx host failed connect over the VMotion network.

You see this error in the /var/log/messages (ESXi host) or /var/log/vmkernel (ESX host) log file:

The ESX hosts failed to connect over the VMotion network Module Migrate power on failed

vmkping testing on the VMkernel network used for vMotion is successful

Note: For more information, see Testing VMkernel network connectivity with the vmkping command (1003728).

Disabling and re-enabling vMotion on the VMkernel port used for vMotion in vCenter does not resolve this issue

In the /var/log/vmkernel log file of the source ESX host, you see this warning:

WARNING: MigrateNet: 210: 4225417790: 2-0x3fa0c8d0:Received only 0 of 68 bytes: Migration protocol error

In the /var/log/vmkernel log file of the destination ESX host, you see these messages:

WARNING: Migrate: 1153: 4225417790: Failed: I/O error (0xbad000a) @0x8d7c03

ESX hosts failed to connect over the VMotion network (0xbad010d) @0x0

Feb 22 14:14:04 esx1 vmkernel: 402:01:22:35.133 cpu6:1939)Migrate: vm 1940: 7338: Setting migration info ts = 1298397818667246, src ip = <192.168.103.48> dest ip = <192.168.103.7> Dest wid = 5272 using SHARED swap
Feb 22 14:14:04 esx1 vmkernel: 402:01:22:35.134 cpu6:1939)World: vm 3330: 900: Starting world migSendHelper-1940 with flags 1
Feb 22 14:14:04 esx1 vmkernel: 402:01:22:35.134 cpu6:1939)World: vm 4355: 900: Starting world migRecvHelper-1940 with flags 1
Feb 22 14:14:04 esx1 vmkernel: 402:01:22:35.136 cpu4:3330)WARNING: MigrateNet: 309: 1298397818667246: 5-0x801f640:Sent only 4020 of 4096 bytes of message data: Broken pipe
Feb 22 14:14:04 esx1 vmkernel: 402:01:22:35.136 cpu4:3330)WARNING: Migrate: 6776: 1298397818667246: Couldn't send data for 8: Broken pipe
Feb 22 14:14:04 esx1 vmkernel: 402:01:22:35.136 cpu4:3330)WARNING: Migrate: 1243: 1298397818667246: Failed: Broken pipe (0xbad0052) @0x9efd5f

The /var/log/vmware/hostd.log (ESX) and /var/log/messages (ESXi) contains an entry similar to:

Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 verbose 'vm:/vmfs/volumes/4c220e6f-01b124b3-f25d-e41f132dae86/twidmann_test/twidmann_test.vmx'] VMotionLastStatusCb: Failed with error 536871181: Failed to start migration pre-copy. Error 0xba
Apr 8 11:24:44 d010d. The ESX hosts failed to connect over the VMotion network.
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 verbose 'vm:/vmfs/volumes/4c220e6f-01b124b3-f25d-e41f132dae86/twidmann_test/twidmann_test.vmx'] VMotionResolveCheck: Operation in progress
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 verbose 'vm:/vmfs/volumes/4c220e6f-01b124b3-f25d-e41f132dae86/twidmann_test/twidmann_test.vmx'] VMotionStatusCb: Completed
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 verbose 'vm:/vmfs/volumes/4c220e6f-01b124b3-f25d-e41f132dae86/twidmann_test/twidmann_test.vmx'] VMotionResolveCheck: Firing ResolveCb
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 info 'VMotionSrc (1302261872027749)'] ResolveCb: VMX reports needsUnregister = false for migrateType MIGRATE_TYPE_VMOTION
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 info 'VMotionSrc (1302261872027749)'] ResolveCb: Failed with fault: (vmodl.fault.SystemError) {
Apr 8 11:24:44 Hostd: dynamicType = <unset>,
Apr 8 11:24:44 Hostd: faultCause = (vmodl.MethodFault) null,
Apr 8 11:24:44 Hostd: reason = "Failed to start migration pre-copy. Error 0xbad010d. The ESX hosts failed to connect over the VMotion network.
Apr 8 11:24:44 Hostd: ",
Apr 8 11:24:44 Hostd: msg = "",
Apr 8 11:24:44 Hostd: }
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 verbose 'VMotionSrc (1302261872027749)'] Migration changed state from MIGRATING to DONE
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 37903B90 verbose 'VMotionSrc (1302261872027749)'] Finish called
Apr 8 11:24:44 Hostd: [2011-04-08 11:24:44.929 366A9B90 info 'vm:/vmfs/volumes/4c220e6f-01b124b3-f25d-e41f132dae86/twidmann_test/twidmann_test.vmx'] Disconnect check in progress.

Resolution

This is a known issue affecting ESXi/ESX 4.0

This issue is resolved in ESXi/ESX 4.0 Update 2 and is being investigated by VMware for the other affected versions.

To download ESXi/ESX 4.0 Update 2, see Download VMware vSphere.

If you cannot upgrade, or you experience these symptoms in a newer version, you can workaround this issue by resetting the Migrate.Enabled setting on both the source and destination hosts.

Note: This issue may re-occur even after applying the workaround.

To reset the Migrate.Enabled setting:

Connect vSphere or VMware Infrastructure Client to your vCenter Server.

Click on the ESX host.

Click the Configuration tab.

Click Advanced Settings under Software.

Select Migrate and change Migrate.Enabled to 0.

Click OK and close.

Click on Advanced Settings.

Select Migrate and change Migrate.Enabled to 1.

Click OK and then Close.

Note: If you see the invalid parametererror after resetting Migrate.Enabled to 1, see Performing a vMotion or adding a network card to a virtual machine fails with the error: Necessary module isn't loaded. (2013128)

If these steps do not resolve the issue, try increasing the timeout for migration network operations after Step 4 and then continue with the remaining steps. Also, ensure to repeat these steps on the destination host.

To increase the timeout for migration network operations:

Click the Configuration tab.

Click Advanced Settings under Software > Migrate.

Change Migrate.NetTimeout to 60 seconds. The default is 20 seconds.

Click OK and then Close.

Note: This issue may also occur due to a duplicate IP address on your network. Ensure that the IP addresses for your vCenter Servers and ESX/ESXi hosts are unique.

Related Information

For more information, see Diagnosing a vMotion failure at 10% or higher in vCenter Server (1003734). Testing VMkernel network connectivity with the vmkping command
Understanding and troubleshooting vMotion
Performing a vMotion or adding a network card to a virtual machine fails with the error: Necessary module isn't loaded
Falha de vMotion a 10% com o erro: Ocorreu um erro geral no sistema: falha na migração ao copiar dados, redirecionamento desfeito
vMotion falla al 10 % con el error: A general system error occurred: Migration failed while copying data, Broken Pipe
vMotion 到 10% 时失败并显示错误：“出现了常规系统错误: 复制数据时迁移失败，管道已损坏”
「一般的なシステム エラーが発生しました：データのコピー中に移行が失敗しました。破損したパイプ」というエラーが発生して vMotion が 10% の時点で失敗する

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

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

Result 1 of 1

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 vSphere ESXi 5.0

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

Support Assistant