The good news is, as soon as I vMotion one of my virtual ESXi servers, the tools do show up as installed
Interesting. Does a full shutdown of a virtual ESXi server followed by a restart fix the problem as well?
Will try to deinstall tools on one of the nested esxi servers to test (all where working now)
After the upgrade I rebooted the nested esxi servers from the cli, so no full shutdown, from the VM
Will let you know
OK, restarted my vCenter Server, tools now show Not Running (Not Installed) on the host
Installed the tools again
Now did a poweroff instead of a reboot in the nested esxi guest after install
Powered on the nested esxi guest
After booting the nested esxi server, VMware Tools still show Running (Not Installed)
Seems like not all info is refreshed in vCenter ...
When restarting vCenter Server again, Status still is Running (Not Installed)
Only after a vMotion status changes to Running (Current)
Just to chip in & say that I have experienced the same behaviour.
Unfortunately I have only one physical host so was unable to vMotion but found that a reboot of the physical host has got it to report properly. To be fair, the graceful power operations worked even when it was reporting not installed.
This appears to be a known hostd bug that can be triggered by a "manual" Tools installation, regardless of guest OS type. It looks like it should be fixed in a future update of ESXi 5.5.
So maybe a "/etc/init.d/hostd restart" might work when done on the physical ESXi host?
(or maybe "services.sh restart")
/etc/init.d/hostd restart AND services.sh restart do work, you can choose which to use.
So no need for vMotion or reboot ...
Message was edited by: Photubias -> Verified
We're experiencing similar issues, though not for nested ESXi-Servers but for regular VMs. If I manually install the tools (9.4.0-1399439 on vSphere 5.5) it succeeds but they show up as "Running (Not Installed)" until I either reboot the vm or vMotion it to another host. Restarting hostd and/or services yields nothing.
We're using puppet to install the tools with all default answers.
Is there any information on when this issue will be resolved?