NOT SOLVED !! : Open-VM-Tools - NOT WORKING on vSphere

[Clouseau]

Ping… anyone?

This issue is now in critical stage. This package breaks pfSense!

[focalguy]

This information would probably be more useful in the ticket:
http://redmine.pfsense.org/issues/1385

[jimp]

Reinstall the package in about 5 minutes, the syntax error should be fixed.

[toomeek]

Hmm..
May I attach something?
QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright 2003-2008 Fabrice Bellard
using KVM.

On Debian I have "virtio-net" NIC attached.
On pFsense I have "Intel E1000" NIC attached, becouse pfSense won't recognize "virtio-net". Shame..

Measured throughput Client (Gigabit NIC) -> VM (attached to Gigabit NIC bridge)
Debian: ~860 Mbps
pfSense: ~260 MBps

Let's do more tests. Using 2.0-RC1 (i386) built on Thu Apr 14 18:50:50 EDT 2011.

[jimp]

That has nothing to do with VMware or VMware tools, start your own thread please.

[JoeUser]

Open-VM-Tools 217847 working on 2.0-RC1 (amd64) built on Sat May 7 23:04:11 EDT 2011.
Tools status in vSphere client shows "Unmanaged", tools are running and kernel modules are present.

[danswartz]

Dunno how many folks know this - I was told this on a vmware forum: people get confused and worried when they see "Unmanaged" for the vm tools status.  That is fine.  What it means is it is vm tools not installed via the esx/esxi interface, do esx/esxi is not managing it for you.  If it said 'not installed' or 'not running', then worry.  HTH.

[Clouseau]

I will have a try tomorrow and hope that tools runs fine. Unmanaged status is just telling that fact that it's not managed by Vmware vSphere client. Vmware should change this status info to something much better (Open Source Tools OK)

[calvinz]

so anyone had luck installing open-vm-tools up to this point ?

[jimp]

@calvinz:

so anyone had luck installing open-vm-tools up to this point ?

As I said earlier in the thread, it loads fine on 32 and 64 bit VMs for me now.

[danswartz]

Ditto here.

[Clouseau]

Confirm! Open-Vm-Tools works again ! Huh….. Nice job! This was an huge problem for me and I'm happy to see this is over.

[jimp]

Glad to hear it worked.

(On an unrelated note I also tackled another 800-pound gorilla, ntop, which should also work now)

[photonman]

I am running a RC1 i386 build from Early april and I just uninstalled my version 2.7xxx vmtools package and installed the latest 3.xxx version and now
my ESX server says the tools status is "unmanaged".

does that mean my vmtools is running?

[cmb]

@photonman:

I am running a RC1 i386 build from Early april and I just uninstalled my version 2.7xxx vmtools package and installed the latest 3.xxx version and now
my ESX server says the tools status is "unmanaged".

does that mean my vmtools is running?

http://forum.pfsense.org/index.php/topic,33587.msg188199.html#msg188199

[photonman]

I got this:

20377  ??  S      0:00.00 sh -c ps ax|grep vmware
20675  ??  R      0:00.00 sh -c ps ax|grep vmware
44364  ??  I      0:21.39 /usr/local/bin/vmtoolsd -c /usr/local/share/vmware-to

$ kldstat
Id Refs Address    Size          Name
1   10 0xc0400000 11426c4  kernel
2    1 0xc762a000 4000       vmmemctl.ko
3    1 0xc76ae000 5000       vmxnet.ko
4    1 0xc76b7000 5000       vmblock.ko
5    1 0xc76bd000 b000     vmhgfs.ko

[Clouseau]

Uups - Open VM Tools for 64bit pfSense works but 32Bit NOT!!

Must reopen this.

Now after reboot I got WARNING: run_rc_command: cannot run /usr/local/bin/vmtoolsd

Argh!!!

Open-VM-Tools are still broken !!

Package version: 313025

[jimp]

Not "still broken". It did work, and there have been commits since to fix other issues that may have broken something again.

[Clouseau]

@jimp:

Not "still broken". It did work, and there have been commits since to fix other issues that may have broken something again.

64bit Open-VM-Tools works still after your fixes. Now I had a try on 32bit and it's not working at all.

[jimp]

See above, re: there have been more commits since I fixed it.

We moved the repositories over to github over the weekend and it's possible some commits didn't happen where they should have. I know someone was working on that package, I'll have to check into it.