Diagnosing VMware VMotion failure at 10%

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

To identify the cause of VMotion failing at 10%:

1. Verify that restarting the VMware Management agents does not resolve the issue. For more information, see Restarting the Management agents on an ESX Server (1003490).
2. Verify that VMkernel networking configuration is valid. For more information, see Unable to set VMkernel gateway as there are no VMkernel interfaces on the same network (1002662).
3. Verify that VMkernel network connectivity exists using vmkping. For more information, see Testing vmkernel network connectivity with the vmkping command (1003728).
4. Verify that Console OS network connectivity exists. For more information, see Testing network connectivity with the Ping command (1003486).
5. Verify that Name Resolution is valid on ESX. For more information, see Identifying issues with and setting up name resolution on ESX Server (1003735).
6. Verify that the required disk space is available. For more information, see Investigating disk space on an ESX host (1003564).
7. Verify that time is synchronized across environment. For more information, see Verifying time synchronization across environment (1003736).
8. Verify that valid limits are set for the virtual machine being VMotioned. For more information, see VMware VMotion fails if target host does not meet reservation requirements (1003791).
9. Verify that hostd is not spiking the console. For more information, see Checking for resource starvation of the ESX Server service console (1003496).
10. Verify that the virtual machine is not configured to use a device that is not valid on the target host. For more information, see Troubleshooting migration compatibility error: Device is a connected device with a remote backing (1003780).