The Virtual machine Summary tab reports the error: The virtual machine inventory file is damaged or unreadable

Products

• VMware vSphere ESXi

Issue/Introduction

The virtual machine Summary tab reports the error:

The virtual machine inventory file is damaged or unreadable

In the hostd log, you see entries similar to:
hostd.log:2012-07-10 [FFD6FAC0 info 'Solo'] VM inventory configuration: /etc/vmware/hostd/vmInventory.xml
hostd.log:2012-07-10 [FFD6FAC0 error 'Default'] Failed to load VM inventory: not well-formed (invalid token)
hostd.log:2012-07-10 [FFD6FAC0 info 'ha-eventmgr'] Event 58 : The virtual machine inventory file on host hostname.xxx.com is damaged or unreadable.
hostd.log:2012-07-10 [FFD6FAC0 info 'Solo'] VM inventory configuration: /etc/vmware/hostd/vmInventory.xml

Environment

VMware vSphere ESXi

Cause

This issue occurs if the vmInventory.xml file is corrupt or damaged.

Resolution

To resolve this issue, review and replace the corrupt/damaged vmInventory.xml file.

 

To replace the vmInventory.xml file:

1. Connect to the host using SSH.
2. Change directories to the location of the vmInventory.xml file using this command:
   
   cd /etc/vmware/hostd
   
   
3. Rename the current inventory file using this command:
   
   mv vmInventory.xml vmInventory.xml.old
   
   
4. Restart management agents on the host using this command:
   
   /sbin/services.sh restart
   
   
5. Perform a migration or vMotion to the ESXi host. This generates a new vmInventory.xml file.

Additional Information

Warning: Performing a vMotion does not include auto-discovery of existing Virtual Machines registered upon a host.

Placing the host into maintenance mode before following these steps will help to avoid manual re-registration of every Virtual Machine on the host.