Within the vSphere client or vCentre your virtual machine(s) are named as ‘Unknown VM’ and are inaccessible.
This can be caused by connectivity issues between the hypervisor and its datastore. To resolve the issue follow these steps,
- Log into the virtual machines host via SSH.
- Then change directory via the command ‘cd /var/lib/vmware/hostd/stats‘.
- List the files in the directory via ‘ls‘. There should be 4.
- Remove the files using ‘rm *‘.
- Then restart the management agents via the command ‘/etc/init.d/hostd restart && /etc/init.d/vpxa restart‘.
~ # cd /var/lib/vmware/hostd/stats /var/lib/vmware/hostd/stats # ls hostAgentStats-20.stats hostAgentStats.idMap hostAgentStats.xml /var/lib/vmware/hostd/stats # rm * /var/lib/vmware/hostd/stats # /etc/init.d/hostd restart watchdog-hostd: Terminating watchdog process with PID 4982 hostd stopped. hostd started. /var/lib/vmware/hostd/stats # /etc/init.d/vpxa restart watchdog-vpxa: Terminating watchdog process with PID 5279 vpxa stopped. /var/lib/vmware/hostd/stats #
- How to Configure a BIND Server on Ubuntu - March 15, 2018
- What is a BGP Confederation? - March 6, 2018
- Cisco – What is BGP ORF (Outbound Route Filtering)? - March 5, 2018
Want to become a VMware expert?
Here is our hand-picked selection of the best courses you can find online:
Complete VMware Administration course
VMware vSphere 7 – Install, Configure, Manage
and our recommended certification practice exams:
AlphaPrep Practice Tests - Free Trial