Latest Posts



Translate

Total Pageviews

Thursday, 2 April 2015

vMotion fails at 90-95% with the error: Operation timed out (1003792)

Symptoms

  • vMotion fails at 90-95%
  • Cannot perform a vMotion
  • vMotion times out
  • In vCenter Server, you see the error:

    Operation timed out
  • vMotion stops at 90% then fails with the error:
    a general system error occurred: failed to resume on destination

cannot-vmotion no-network-vmotion vmotion-fails vmotion-fails-between-90%-95%

Purpose

This article guides you through the process of diagnosing issues that may cause vMotion to fail at 90-95%.

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, 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. Do not skip a step.
  1. If the virtual machine being vMotioned is a 64-bit virtual machine, verify that the VT option is enabled on both of your ESX hosts.For more information, see vMotion fails at 90% with message: A general system error occurred: failed to resume on destination (1008735).
  2. Restart the host management agents. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490).
  3. Verify that time is synchronized across your environment. For more information, see Verifying time synchronization across an ESX/ESXi host environment (1003736).
  4. 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).
  5. Verify that host management agents are not spiking the Service Console (ESX only).  For more information, see Checking for resource starvation of the ESX Service Console (1003496).
  6. Verify that there are no issues with the shared storage. For more information, see Identifying Fibre Channel, iSCSI, and NFS storage issues on ESX/ESXi hosts (1003659).
Note: If your problem still exists after trying the steps in this article: