Search the VMware Knowledge Base (KB)
View by Article ID

Re-registering orphaned virtual machines (1007541)

  • 17 Ratings

Symptoms

  • Virtual machines that are running and fully functional in vCenter Server do not display correctly in the Inventory view of the ESX/ESXi host on which they are registered.  
  • Virtual machines appear in an Orphaned state in vCenter Server.
  • Removing the host from vCenter Server does not resolve the Orphaned state.
  • The vm-support -x command does not contain all of the virtual machine's registered on the host.
  • When the host is re-added to inventory, vCenter Server reports this error:

    Not enough licenses to perform this operation

  • The vCenter Server log file contains this error from Licmgr:

    Bad host information for host

  • The vpxa.log file on the ESX host contains the error:

    [2008-11-05 15:13:52.869 'App' 7490480 warning] ============BEGIN FAILED METHOD CALL DUMP============
    [2008-11-05 15:13:52.870 'App' 7490480 warning] Invoking [GetLayout] on [vim.VirtualMachine:10496]
    [2008-11-05 15:13:52.870 'App' 7490480 warning] Fault Msg: "A general system error occurred: Failed to serialize result"
    [2008-11-05 15:13:52.870 'App' 7490480 warning] ============END FAILED METHOD CALL DUMP============

Cause

This issue may be caused by a corrupt inventory file on the ESX host.

Resolution

To clear the existing host inventory and re-register the orphaned virtual machines on the affected host:
  1. Open the VMware Infrastructure Client (VI) and connect to vCenter Server with administrative privileges.
  2. Attempt to register the virtual machine manually.

    For more information see, Registering or adding a virtual machine to the inventory (1006160). If the operation fails, proceed to the next step.


  3. Put the host into maintenance mode. For more information, see Place a Host in Maintenance Mode section of the vSphere Upgrade guide.
  4. Right-click the host and remove it from the inventory.

    Note: If the ESX(i) host is apart of the Virtual Distributed Switch (VDS), you will need to remove it from the VDS before removing from inventory. For more information, see Attempting to remove a host from the inventory when it is connected to vDS generates an error (1018181).

  5. Log in to the host as root.

    For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807).


  6. Make a backup copy of the existing inventory file for the host.

    For ESX 3.0 hosts, run the command:

    cp /etc/vmware/vmInventory.xml /etc/vmware/vmInventory.xml.backup

    For ESX 3.5 and ESX/ESXi  4.x and  5.x  hosts, run the command:

    cp /etc/vmware/hostd/vmInventory.xml /etc/vmware/hostd/vmInventory.xml.backup 
     
  7. Clear the contents of the vmInventory.xml file.

    For ESX 3.0 hosts, run the command:

    cat /dev/null > /etc/vmware/vmInventory.xml

    For ESX 3.5 and ESX 4.0 hosts and later, run the command: 

    cat /dev/null > /etc/vmware/hostd/vmInventory.xml
     
  8. From VI Client, add the ESX host back to vCenter Server.
  9. Register the virtual machine manually.

    For more information see, Registering or adding a virtual machine to the inventory (1006160).

See Also

Update History

04/19/2010 - Added ESX 4.0 to Products 10/01/2012 - Updated Product Versions with 4.x and 5.x for ESX and VC

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

  • 17 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)




Please enter the Captcha code before clicking Submit.
  • 17 Ratings
Actions
KB: