NOT SOLVED !! : Open-VM-Tools - NOT WORKING on vSphere
-
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
-
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 -
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
-
Not "still broken". It did work, and there have been commits since to fix other issues that may have broken something again.
-
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.
-
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.
-
Give it about 10 minutes and try to reload the package again.
-
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.
-
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.
-
ok, I'm seeing that too. The KLDs are loaded but the guest daemon isn't. Shouldn't be hard to fix.
-
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.
-
And that command runs fine for me, and the daemon continues to run once I start it by hand.
-
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?
-
Do you have problems on both 64-bit and 32-bit VMs?
My 64-bit RC2 loads up fine (I think)
no error messages
-
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/vmtoolsdFor 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) -
Jimp:
$ file /usr/local/bin/vmtoolsd /usr/local/bin/vmtoolsd: cannot open `/usr/local/bin/vmtoolsd' (No such file or directory)and
$ ldd /usr/local/bin/vmtoolsdSomething is totally wrong here, but what can you really do wrong? Bad mouse click on install package ;D
I got version:
2.0-RC2 (i386)
built on Sun May 15 20:43:07 EDT 2011Problems are now only on 32bit pfSense.
-
Either the package isn't getting fully installed somehow, or it thinks it is installed but really isn't.
Uninstall the vmware tools package, and then run:
pkg_infoAnd then report the results back here. Odds are there is something in the list that, once you pkg_delete -f it, things will start to work properly.
Sure, all you did was click the mouse, but odds are that something in the underlying OS is the real issue, especially since it seems unique to just you.
-
I run your command: pkg_info:
$ pkg_info grub-0.97_3 GRand Unified Bootloader packages BSD Installer mega-package python26-2.6.5 An interpreted object-oriented programming languageI run commands:
pkg_delete -f grub-0.97_3 pkg_delete -f packages pkg_delete -f python26-2.6.5Now everything seems to be clear.
After this I installed Open-VM-Tools again.
And logs says that vmware tools are not running!
Jun 13 14:06:24 kernel: VMware memory control driver initialized Jun 13 14:06:24 root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: failed to start vmware_guestdNow I run pkg_info again:
fusefs-kmod-0.3.9.p1.20080208_7 Kernel module for fuse fusefs-libs-2.7.4 FUSE allows filesystem implementation in userspace libdnet-1.11_3 A simple interface to low level networking routines libiconv-1.13.1_1 A character set conversion library open-vm-tools-nox11-313025_2 Open VMware tools for FreeBSD VMware guests pcre-8.12 Perl Compatible Regular Expressions library pkg-config-0.25_1 A utility to retrieve information about installed librariesSo, this issue is not solved! Should I pkg_delete all these packages now?
-
Don't pkg_delete those, try to find out more about why it can't start vmware-guestd.
What does this output?
ldd /usr/local/bin/vmtoolsd -
$ 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 => not found (0x0) libgobject-2.0.so.0 => not found (0x0) libgthread-2.0.so.0 => not found (0x0) libglib-2.0.so.0 => not found (0x0) libintl.so.9 => /usr/local/lib/libintl.so.9 (0x28123000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2812c000) libpcre.so.0 => /usr/local/lib/libpcre.so.0 (0x28222000) libicui18n.so.46 => not found (0x0) libicuuc.so.46 => not found (0x0) libicudata.so.46 => not found (0x0) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x2825e000) libm.so.5 => /lib/libm.so.5 (0x28352000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2836c000) libc.so.7 => /lib/libc.so.7 (0x28377000) libglib-2.0.so.0 => not found (0x0) libicui18n.so.46 => not found (0x0) libicuuc.so.46 => not found (0x0) libicudata.so.46 => not found (0x0)
