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

[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.

[jimp]

Give it about 10 minutes and try to reload the package again.

[jimp]

Actually the package sync was broken since the move to github, try it now and see if it's any better. I just fixed the package sync.

[secabeen]

This package looks like it installs and runs successfully, but doesn't start properly on bootup.  I can run the scripts in /usr/local/etc/rc.d/, but if I reboot the PFSense VM, when it comes back up, the vmware daemon and kernel modules aren't loaded.

[jimp]

ok, I'm seeing that too. The KLDs are loaded but the guest daemon isn't. Shouldn't be hard to fix.

[Clouseau]

@secabeen:

This package looks like it installs and runs successfully, but doesn't start properly on bootup.  I can run the scripts in /usr/local/etc/rc.d/, but if I reboot the PFSense VM, when it comes back up, the vmware daemon and kernel modules aren't loaded.

true, it installs just fine without any errors but vmtools just are not starting. I Still go this error: root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: run_rc_command: cannot run /usr/local/bin/vmtoolsd

This is only package I use in my system.

[jimp]

And that command runs fine for me, and the daemon continues to run once I start it by hand.

[secabeen]

@Clouseau:

@secabeen:

This package looks like it installs and runs successfully, but doesn't start properly on bootup.  I can run the scripts in /usr/local/etc/rc.d/, but if I reboot the PFSense VM, when it comes back up, the vmware daemon and kernel modules aren't loaded.

true, it installs just fine without any errors but vmtools just are not starting. I Still go this error: root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: run_rc_command: cannot run /usr/local/bin/vmtoolsd

This is only package I use in my system.

Do you have problems on both 64-bit and 32-bit VMs?

[photonman]

@secabeen:

Do you have problems on both 64-bit and 32-bit VMs?

My 64-bit RC2 loads up fine (I think)

no error messages

[jimp]

@Clouseau:

true, it installs just fine without any errors but vmtools just are not starting. I Still go this error: root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: run_rc_command: cannot run /usr/local/bin/vmtoolsd

This is only package I use in my system.

You appear to have an issue that nobody else seems to have. Try these commands, and show the output:

file /usr/local/bin/vmtoolsd
ldd /usr/local/bin/vmtoolsd

For comparison, I get this output on my system:

: file /usr/local/bin/vmtoolsd
/usr/local/bin/vmtoolsd: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.1, stripped
: ldd /usr/local/bin/vmtoolsd
/usr/local/bin/vmtoolsd:
        libvmtools.so.0 => /usr/local/lib/libvmtools.so.0 (0x2809a000)
        libcrypt.so.5 => /lib/libcrypt.so.5 (0x280f5000)
        libthr.so.3 => /lib/libthr.so.3 (0x2810e000)
        libgmodule-2.0.so.0 => /usr/local/lib/libgmodule-2.0.so.0 (0x28123000)
        libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0 (0x28127000)
        libgthread-2.0.so.0 => /usr/local/lib/libgthread-2.0.so.0 (0x2816a000)
        libglib-2.0.so.0 => /usr/local/lib/libglib-2.0.so.0 (0x2816f000)
        libintl.so.9 => /usr/local/lib/libintl.so.9 (0x28241000)
        libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2824a000)
        libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28340000)
        libicui18n.so.46 => /usr/local/lib/libicui18n.so.46 (0x2837c000)
        libicuuc.so.46 => /usr/local/lib/libicuuc.so.46 (0x2855e000)
        libicudata.so.46 => /usr/local/lib/libicudata.so.46 (0x28694000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x29513000)
        libm.so.5 => /lib/libm.so.5 (0x29607000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x29621000)
        libc.so.7 => /lib/libc.so.7 (0x2962c000)