[Guide] Managing corrupted / unaccessible / unknown / invalid VMs from the ESXi host
- Too many snapshots (32 or more) are created
- The virtual machine configuration file is corrupt
- The virtual machine guest operating system is not supported
- In a SSH/Putty connection, connect to the ESX host.
- Backup the /etc/vmware/hostd/vmInventory.xml file.
- Run the command:
mv /etc/vmware/hostd/vmInventory.xml /etc/vmware/hostd/vmInventory.xml.bak
- Restart the hostd process. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490).
- Right-click the ESX host and choose Connect.
If the ESX host connects successfully, then a corrupt virtual machine is preventing your ESX host from connecting to the vCenter Server inventory.
Note: After performing these steps, all of the virtual machines appear orphaned in vCenter Server. If you connect directly to the ESX host, you do not see any virtual machines.
To resolve this issue, open the vmInventory.xml file, and add one virtual machine entry from the vmInventory.xml.bak file at a time, then add the ESX host into inventory until you have determined the problematic virtual machine.