Marcelo,
Petr,
Is the "bug" in vSphere 4.x flaky enough for the tools status
to occasionally be reported as "unmanaged" for unsupported guests?
- yesterday my OSR6 VM was "Unmanaged" for several reboots
and restarts of the vmtoolsd
- today, following a power-hit to our Intel Modular Servers,
an OSR507 VM was rebooted and is reporting a VMtools status of
"Unmanaged" - through several shutdown and power-up cycles.
Previously the status was being reported as "Not Installed".
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?
-- John
Marcelo Vanzin wrote:
> Hi John,
>
> On 07/21/2011 01:32 PM, John Wolfe wrote:
>
>> Jul 21 14:24:12.732: vcpu-1| VMXVmdb_SetToolsVersionState: status value set
>> to
>> 'notAvailable'
>>
>
> I'm pretty sure this is a bug in VMware's host code, so there's nothing you
> can
> do from the Tools side. Someone else reported a similar issue here before, and
> we've already fixed the host code in the vSphere 5.0 release. (I don't think
> the
> fix was backported to any maintenance release of previous vSphere versions.)
>
>
------------------------------------------------------------------------------
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
