VMware
 

Knowledge Base

Search the Knowledge Base:

Products:
Search In:
 

Diagnosing VMware VMotion failure at 10%

Symptoms

  • VMware VMotion fails at 10% of migration complete
  • VMotion times out
  • The following messages are produced in VirtualCenter:
    • Migration will cause the virtual machine's configuration to be modified to preserve the CPU feature requirements for it's guest operating system.
    • Operation timed out
    • A general system error occurred:
      Failed waiting for data. Error 16. Invalid argument

Purpose

This article guides you through diagnosing any issues that may have caused VMware VMotion to fail at 10%.

Resolution

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).
Note: If your problem still exists after trying the steps in this article, please:

Additional Information

As per ftPerl consumes 100% CPU after enabling VMware High Availability (1012871), an issue with ftPerl may cause VMotion failures at 10%. This issue has been resolved in VirtualCenter 2.5 Update 5 and vCenter Server 4.0, which are available from the VMware Download Center.

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (6 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (6 Ratings)   
Actions