This seems to have resolved my issue where every vMotion failed at 14% reporting “A general system error occurred: Migration to host <IP address> failed with error Busy (0xbad0004).”
vMotion fails with the error: remote host IP_Address failed with status Busy (1031636)
This issue may occur:
Due to the slight difference in the type of swap files in ESX 4.1 and earlier ESX versions.
When performing a vMotion of a virtual machine which has its virtual swap file (.vswp) stored on an NFS datastore.
This issue is resolved in ESX/ESXi 4.1 Update 2 and ESXi 5.0. For more information, see the ESX/ESXi 4.1 Update 2 Release Notes.
To download ESX/ESXi 4.1 Update 2, see the VMware Download Center.
To workaround this issue when you do not want to upgrade, you must modify the swap type setting on both the source and target host.
To modify the setting:
Launch the vSphere Client and log in to your vCenter Server.
Select the source ESX host and then click the Configuration tab.
Click Software > Advanced Settings > Migrate.
Under the Migrate options, locate the line containing Migrate.VMotionResolveSwapType. By default, it is set to 1.
Change the value to 0.
Repeat Steps 2 to 6 for the destination host.
via VMware KB: vMotion fails with the error: remote host IP_Address failed with status Busy.