Users report that while they can successfully log in to the vSphere Client via the HTML5 UI, the inventory pane fails to display any objects such as hosts, VMs or clusters. The interface appears blank or stuck loading.
Preliminary diagnostics indicate:
vmware-vpxd service is consuming an abnormally high percentage of CPU resources as seen in top.vmkernel.log has stopped updating.
The vmware-vpxd service has entered a hung state and is consuming excessive CPU resources, preventing the vSphere Client from rendering inventory data. This state is frequently observed in environments with prolonged uptime exceeding 1 year, where regular maintenance windows, service restarts, or critical patches have not been applied.
Contributing factors identified in this scenario include:
To restore immediate access to the inventory, the vCenter service must be restarted. A subsequent maintenance window is required to address the root stability issues on the hosts.
service-control --stop vmware-vpxd
service-control --start vmware-vpx
Log out and log back in to the vSphere Client to verify the inventory is visible.
Ensure routine maintenance windows are scheduled to apply security patches and reboot components to prevent resource exhaustion associated with extreme uptime.