Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

vMotion fails with the error: A general system error occurred. Invalid fault (1014371)

Symptoms

  • vMotion operation of a virtual machine fails
  • You see this error:

    A general system error occurred. Invalid Fault

  • After the vMotion failure, if the virtual machine is powered-on, it becomes available on the network, but is not accessible in vCenter Server
  • In the /var/log/vmware/hostd.log file of the ESX hosts, you see entries similar to:

    [2009-09-01 23:31:19.697 'VMotionSrc (1251862166980371)' 88214448 info] ResolveCb: VMX reports gone = false
    [2009-09-01 23:31:19.698 'VMotionSrc (1251862166980371)' 88214448 info] ResolveCb: Failed with fault: (vim.fault.Timedout) {
       dynamicType = <unset>,
       msg = ""
    }
    [2009-09-01 23:50:25.923 'ha-eventmgr' 3076449440 info] Event 1 : Configuration file for  on <hostname> in ha-datacenter cannot be found
    [2009-09-01 23:50:25.923 'vm:/<path to vmx>' 3076449440 info] State Transition (VM_STATE_INITIALIZING -> VM_STATE_INVALID_LOAD)
    [2009-09-01 23:50:25.924 'vm:/<path to vmx'> 3076449440 info] Marking VirtualMachine invalid

Resolution

This issue may occur if the .vmx configuration file of the virtual machine cannot be located. The virtual machine's datastore may be resignatured, or the virtual machine folder may be renamed or moved.
 
If the virtual machine's folder or the .vmx file has been renamed or moved:
  1. Shut down the virtual machine using a RDP, Citrix, or SSH connection.
  2. In the vSphere client connection to vCenter Server, right-click the virtual machine and click Remove from Inventory.
  3. Locate the virtual machine folder and configuration file using one of these methods:
    1. Use the vSphere clients Datastore Browser. For more information, see the Working with Files in the Datastore Browser section of the Basic System Administration Guide.
    2. Connect to the ESX host as root using an SSH client.

      Note: For more information, see Connecting to an ESX host using a SSH client (1019852).


    3. Run this command to determine the UUID of the datastore of the .vmx file:

      find /vmfs/volumes -name vmname.vmx -print

      Note: The .vmx file name in this command is case sensitive. If you are uncertain of the case, use -iname instead of -name.


    4. To correlate the datastore UUID with the datastore name, run this command:
      • In ESX – vdf
      • In ESXi – df

        Note: Alternatively, you can use the ls -l /vmfs/volumes command to determine the UUID of datastores.

  4. If the .vmx file for the virtual machine is found and the datastore name is identified in Step 3, add the virtual machine back to inventory. For more information, see the Return a virtual machine or Template to vCenter Server portion section of the Basic System Administration Guide.

Additional Information

The issue may also appear due to storage issues.  A rescan of the storage may also resolve this issue.  For more information see, Performing a rescan of the storage on an ESX/ESXi host (1003988)

See Also

Update History

04/11/2013 - Added alternative command to determine the UUID of the datastore

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 8 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? (4000 or fewer characters)
  • 8 Ratings
Actions
KB: