VMotion fails at 10 percent

Posted: June 22, 2011 in VMware
Tags: ,

A common problem I see is when VMotion fails at the 10% mark with a timeout. You might see a dialog popup which says-

Operation timed out
Tasks: A general system error occurred:
Failed waiting for data. Error 16. Invalid argument

The VMware Knowledgebase writers have assembled a great list of possible reasons for this problem and I keep a printed out copy on my cubicle wall for this (ie: I didn’t write this)

Each step provides instructions or a link to a document with further details on how to eliminate possible causes and take corrective action to resolve the timeout. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.

  1. Verify that restarting the VMware Management Agents do 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 time is synchronized across environment. For more information, see Verifying time synchronization across environment (1003736).
  7. Verify that valid limits are set for the VM being VMmotioned. For more information, see VMware VMotion fails if target host does not meet reservation requirements (1003791).
  8. Verify that hostd is not spiking the console. For more information, see Checking for resource starvation of the ESX Server service console (1003496).
  9. Verify that VM is not configured to use a device that is not valid on target host. For more information, see Troubleshooting migration compatibility error: Device is a connected device with a remote backing (1003780).

***UPDATE (2/12/2010) There is now a great video on YouTube on how to fix this problem here: http://www.youtube.com/watch?v=42n-osx64ek

Note: If VMotion continues to fail at 10 percent after trying the steps in this article, open a case with tech support

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s