Virtual machine IP address is missing in vCenter Client with unresponsive Guest OS

Products

• VMware vSphere ESXi

Issue/Introduction

In vSphere environments, virtual machines may fail to display an IP address on the vSphere Client Summary tab. Additionally, administrators or end-users may experience the following symptoms:

• Unable to establish remote connections (e.g., SSH, RDP) or log into the Guest OS.

• Direct VM console access is unresponsive or unmanageable.

• Migrating the VM to another host via vMotion does not resolve the issue.

Environment

 

• VMware vCenter Server 8.0.3

• VMware ESXi 8.0.x

 

Cause

This issue occurs when the VMware Tools service (vmtoolsd) within the Guest OS becomes uncommunicative, stopped, or hung. Because the Guest OS is unresponsive, VMware Tools cannot transmit guest network configuration metrics (such as the IP address) across the Guest RPC channel back to the ESXi host and vCenter Server.

Resolution

To resolve this issue,

Step 1 

   1. If the guest OS is unresponsive, restart the virtual machine.  

   2. If the guest OS is running, verify if restarting the VMware Tools service within the guest OS resolves the issue.  


Step 2 

If guest OS becomes responsive but VMware tools service is still stopped or hunged, 

Perform a clean reinstallation of VMware Tools and verify Guest OS service state:

1. Log into the Virtual Machine via the vSphere Web Console or VMRC.

2. If the Guest OS remains unresponsive, restart the Virtual Machine from the vSphere Client.

3. Log into the Guest OS with administrative privileges.

4. Uninstall the existing VMware Tools installation.

5. Reboot the Guest OS.

6. Manually purge leftover VMware Tools installation directories (e.g., C:\Program Files\VMware\VMware Tools on Windows).

7. Verify that third-party security software or antivirus agents inside the Guest OS are temporarily disabled or configured with exclusions for vmtoolsd.exe.

8. Mount the VMware Tools ISO from the vSphere Client and execute a full installation.

9. Reboot the Guest OS to complete the installation.

Additional Information

 

• Per Broadcom operational guidelines, local Guest OS level configurations or OS hang conditions may require engagement with your internal OS/System Administration team if the OS remains unresponsive after rebooting.

• IP address and other information are not displayed in vSphere Client