Hi John, On 07/21/2011 03:01 PM, John Wolfe wrote: > Is the "bug" in vSphere 4.x flaky enough for the tools status > to occasionally be reported as "unmanaged" for unsupported guests?
The flakiness of the status does look weird; but looking at the fix for the bug, it does seem like it would properly handle this case. The bug was that the status could be set to "not installed" if the configured guest OS did not have a VMware tools package (which would be the case for "other" or "sco" guest OS types). I don't know if "could" there means that the status would always be set to "not installed". But with the fix, if the Tools version is "unmanaged", that's always properly reported, regardless of the OS type. > Is there anything that I can do to reduce the number of tools > running, not running, version not available, not installed > messages that are being dropped into /var/log/vmware/hostd.log? The workaround that the user who first complained used was to set up the VM as "linux" or "linux 64-bit". That would work around this particular bug, since we do have a Tools package for Linux. I'm not sure whether ESX 4.1 has a specific guest os type for SCO. I think we have some internal tweaks for SCO regarding time keeping, that are only applied if you choose the appropriate guest OS type. So changing it to Linux might have some adverse side-effects. -- - Marcelo ------------------------------------------------------------------------------ 5 Ways to Improve & Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/ _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
