Hi Mark, You're probably not going to have much luck getting help with open-vm-tools from VMware's tech support. That being said, I have no idea what they mean by open-vm-tools not logging properly on ESXi.
On 05/02/2011 09:07 AM, Mark Felder wrote: > We're having issues with FreeBSD on our VMWare cluster since around > October. VMs (usually higher load ones) will see a spike of CPU in VMWare > and they'll become mostly unresponsive. No more network communication, and > on the console you can sometimes switch VTs and type but nothing really > happens. You have to give it a hard reboot. You can add these lines to /etc/vmware-tools/tools.conf: --------- [logging] log = true vmsvc.level = debug vmsvc.handler = vmx -------- And the logs will show up in your VM's vmware.log on the host. That avoids having to be able to log into the VM to collect the logs. This will work with recent o-v-t versions, but not with the stable 8.4.2 version or with your official VMware version, since none of the currently released versions have that feature. For those you'd have to use this: --------- [logging] log = true vmsvc.level = debug vmsvc.handler = file vmsvc.data = /path/to/logfile -------- And then collect the log from the VM. If you want to experiment, you can start disabling different plugins by removing the .so file from the plugins directory on your VM, and restarting the Tools services. That's assuming that the spike in CPU is caused by one of the vmtoolsd processes in your VM. -- - Marcelo ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
