NOT SOLVED !! : Open-VM-Tools - NOT WORKING on vSphere
-
Any news about this huge problem? 64bit and 32bit tools are now broken. This is now a "show stopper issue" at VMware vSphere environment.
-
Can you use the proprietary drivers in the meantime like I described in the first page of this thread? This was working fine for me for a very long time since the Alpha version days of 2.0
-
My VM Tools installed fine. It says "Unmanaged" in VMWare but I believe that's just because it's the open version of the tools which don't have all the features.
pfSense Version: 2.0-RC1 (amd64) built on Sat Feb 26 18:07:23 EST 2011
Open-VM-Tools Version: 217847 -
What is Open-vm-tools? Something like Virtualbox-additions (paravirtualized drivers)?
Uh, never used, don't have to.
I just use Qemu-KVM and rtl8139/e1000 standard network devices. I would like to test performance, but I see "iperf" package is not available to download in Beta.
I use 2.0-RC1 (i386) built on Fri Apr 15 14:44:27 EDT 2011.EDIT: sorry, I missed "Add" button.
Yes, You're correct. They are needed. Just never used more than 20Mbits before.
Tested both - from hypervisor (it has nVidia Corporation MCP61 Ethernet Gigabit NIC) and from client with 1Gbit NIC. Both reached ~50Mbits.EDIT: Just tested again on Dell PowerEdge R310 with 2 x "Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet" and reached ~73Mbits on "e1000" network device.
Oh, good to know that. I was planning to use virtualized pfSense as a router for LAN traffic too (routing traffic between 2 subnets). Becouse of heavy load (IP cameras, printers) I need to reach 1Gbit or more for that.
-
Onhel: No I can't. I must and want to use "native" psSense package menu drivers aka Open-VM-Tools. Now I understand why not to use open source drivers. Poor and extremely slow support :-[ Community idea is not working here at all. Now the installation fails just for missing package icu-4.6.1.tbz. This has been the situation for long time now. This is situation in 32bit version. With 64bit version there is other major show stopper issues. (yeah - I'm a bit frustrated now)
I just can't understand how this can have a STABLE status on package list? "Open-VM-Tools: Stable 313025 platform: 2.0"
A totally non working package installer and status is STABLE?installation@ESXi: 2.0-RC1 (i386) built on Sun Apr 17 04:28:14 EDT 2011
Downloading http://files.pfsense.org/packages/8/All/icu-4.6.1.tbz … could not download from there or http://ftp2.FreeBSD.org/pub/FreeBSD/ports/i386/packages-8.1-release/All/icu-4.6.1.tbz.
of icu-4.6.1 failed!Installation aborted.Backing up libraries.
-
Disregarding the present openvmtools issues, any advantages using amd64 versus i386 on esxi?
-
Hi,
I'm using pfSense 32bits on VMWare ESXi.
Concerning package installation issue, Martin(mfuchs) has recently made progress but it seems that the last problem is availibility of icu-4.6.1.tbz.
Do you think it's possible to sync this file from Martin (http://pfsense.trendchiller.com/packages/icu-4.6.1.tbz) to the pfsense one (http://files.pfsense.org/packages/8/All/)?
Thanks for all your effort!
-
Hi,
I'm using pfSense 32bits on VMWare ESXi.
Concerning package installation issue, Martin(mfuchs) has recently made progress but it seems that the last problem is availibility of icu-4.6.1.tbz.
Do you think it's possible to sync this file from Martin (http://pfsense.trendchiller.com/packages/icu-4.6.1.tbz) to the pfsense one (http://files.pfsense.org/packages/8/All/)?
Thanks for all your effort!
This missing icu-4.6.1.tbz package has been synced at 29'th April, has anyone tryed the installation after this? I will do it tomorrow but I'm interested to hear if this issue now fixed?
-
Hi
This missing icu-4.6.1.tbz issue is resolved, but OpenVM Tools hangs on installation. Tested on yesterday on 2 installations, will try today for more investigation.
But thanks for correction :)
Best regards -
okey,
I made an upgrade test again. Open-VM-Tools fails to install. There is some kind of parse error(Syntax error) on line 13.
Now Dashboard shows all the time that some "Packages are currently being reinstalled in background". But the reality is that there is nothing packages in reinstallation (only Open-VM-Tools hangs this process) I had to reboot the firewall - now no access to firewall web GUI !! Had to reboot webConfigurator to gain access again. Now - no access to WAN network. It totally lost it's connectivity. Then I tried to remove the Open-VM-Tools package. No luck there. Even this hangs up now. It seems to stuck in "Loading package instructions…"
My pfSense is now dead - R.I.P 8)
This situation has changed from bad to worse! Open-VM-Tools installation problem is now CRITICAL!
-
Ping… anyone?
This issue is now in critical stage. This package breaks pfSense!
-
This information would probably be more useful in the ticket:
http://redmine.pfsense.org/issues/1385 -
Reinstall the package in about 5 minutes, the syntax error should be fixed.
-
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 MBpsLet's do more tests. Using 2.0-RC1 (i386) built on Thu Apr 14 18:50:50 EDT 2011.
-
That has nothing to do with VMware or VMware tools, start your own thread please.
-
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. -
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.
-
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)
-
so anyone had luck installing open-vm-tools up to this point ?
-
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.
-
Ditto here.
-
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.
-
Glad to hear it worked.
(On an unrelated note I also tackled another 800-pound gorilla, ntop, which should also work now)
-
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?
-
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/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)
-
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/vmtoolsd
Something 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.