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

[AhnHEL]

Did several installs a couple of days ago trying to iron out an issue with my pfsense box and tried out the OpenVM Tools package again.  Got the Unmanaged status, IP address, DNS name and Host.  Seemed to be working just fine on my ESXi setup.

[Clouseau]

@onhel:

Did several installs a couple of days ago trying to iron out an issue with my pfsense box and tried out the OpenVM Tools package again.  Got the Unmanaged status, IP address, DNS name and Host.  Seemed to be working just fine on my ESXi setup.

I have istalled 2.0-RC1 (i386) built on Wed Mar 9 18:16:20 EST 2011. Open-VM-Tools Package 217847, 3 network adapters with Adapter type E1000.

One pfSense has now Unmaneged status and one Not installed status. Both pfSenses has the same version. All the Interfaces has manual ip-settings. No dhcp in use. Funny but I don't have any success to get any interface information.

Host Server: Dell PowerEdge 2950, 16GB RAM, 8 CPU cores x2,659GHzRAM, Intel Xenon E5430@2,66GHz
VMware vSphere 4.1.0 U1 Build 348481

Does non of you have this issue?




[regis]

I'm also experiencing strange behavior with open-VM-tools. It shows as unmanaged in Vsphere client and no information displayed about ip adresses and hostname, just like you.

I'm using pfSense 2.0-RC1 (i386) built on Mon Mar 14 11:25:06 EDT 2011 on ESXi 4.1.0,260247, em adapters

But even worse, with open-VM-tools installed, it seems that packets are dropped or lost. MSN messenger keeps disconnecting every 30s or so, downloads stalls after 30s

Once open-VM-tools package deleted and pfSense rebooted, everything's fine…

[Clouseau]

Okey, I'n not alone  ;D

I'm been banging my head to the wall (not helping any) with this issue. I'm lucky that I don't have any usability issues like regis. I have not done any "stress test" to pfSense with vm-tools installed just to figure out is there any major issues.

I really hope that develepers of vm-tools picks this problem up. Open-VM-Tools is only needed in virtualized environments and now it's non working => Open-Vm-Tools package is proken!

[focalguy]

@onhel:

Did several installs a couple of days ago trying to iron out an issue with my pfsense box and tried out the OpenVM Tools package again.  Got the Unmanaged status, IP address, DNS name and Host.  Seemed to be working just fine on my ESXi setup.

I'm not sure what the differences are. I'm not on the latest snapshot but I have it working just the same with showing my IPs and hostnames, etc. I'll update to the latest tonight and see if it continues to work.

[Sloth]

Open-VM-Tools working fine for me:
ESXi 4.1 update 1
pfSense 2.0-RC1 (amd64) built on Sat Feb 26 18:07:23 EST 2011

'Unmanaged' status indicates that  VM tools are installed on the guest VM, but do not support  installation/update from the ESX console, afaik the correct status for a pfsense install.

Jason.

[Clouseau]

@Sloth:

Open-VM-Tools working fine for me:
ESXi 4.1 update 1
pfSense 2.0-RC1 (amd64) built on Sat Feb 26 18:07:23 EST 2011

'Unmanaged' status indicates that  VM tools are installed on the guest VM, but do not support  installation/update from the ESX console, afaik the correct status for a pfsense install.

Jason.

Yes true - but that does not explain the situation that I have 2 pfSense installations in the same vSphere ESXi - one has Unmanaged and the second one is Not installed status on ESX console. Neither of those are capable to show interface information, dns information etc..

[Sloth]

The only other thing of note is that the current pfSense package version of Open-VM-Tools is quite old, dating back to 12-2009. There is a thread somewhere on this forum discussing the issue, which (if I remember correctly) comes down to the freeBSD maintainers updating the freeBSD package to the most current release Open-VM-Tools build i.e. not a lot the pfSense team can do about it. I have had problems trying to use the enhanced VMXNET2 driver, and VMXNET3 is not available, both of which may well be addressed by an up-to-date Open-VM-Tools freeBSD package.

I'll try spinning up a pfSense VM with the pfSense build you are using to see whether I suffer the same issue with that build (could be a 32bit specific issue).

Jason.
2.0-RC1 (amd64) built on Sat Feb 26 18:07:23 EST 2011

[sburgiel]

@Clouseau:

Yes true - but that does not explain the situation that I have 2 pfSense installations in the same vSphere ESXi - one has Unmanaged and the second one is Not installed status on ESX console. Neither of those are capable to show interface information, dns information etc..

What other packages do you have installed on your virtual pfSense boxes, are the same packages installed on both boxes, and what NICs are your pfSense boxes using?

I have been successfully running a pfSense box on VMware ESXi since ESXi 4.0.0 (currently using ESXi 4.1.0 SP1).  My virtual pfSense box only has the Open-VM-Tools package installed, uses virtual Intel e1000 NICs, and has always shown the correct information on the VMware console.

[regis]

'Unmanaged' status indicates that  VM tools are installed on the guest VM, but do not support  installation/update from the ESX console, afaik the correct status for a pfsense install.

You're right but I have several pfSense 1.2.3-RELEASE virtual machines on the same ESXi host with openVM-tools installed, they also shows as unmanaged but the IP adresses of the interfaces can be read from the vsphere client , along with the hostname. This doesn't work with open-VM-tools on pfSense 2.0-RC1

They all use the same virtualized hardware, e1000 NICs (em driver), open-VM-tools is the only package installed.

[Clouseau]

I tryed 64Bit pfSense 2.0 RC1 Wed Mar 16 2011

!! Open-VM-Tools works !!

==> This is 32bit psSense issue !!

[Sloth]

Yup - have tried a couple of 32bit builds: the one you are using and the 'official' RC-1 build (Feb 26), with E1000 NICs installed, and neither show interface IPs in VSphere console. As mentioned above, I have not had any problems with my pfSense VM installs, but I have only run '1.2.3 release' and '2.0 AMD64' builds.

I also noticed that the Open-VM-Tools package has a different version name to that reported in package manager:

http://files.pfsense.org/packages/8/All/open-vm-tools-nox11-313025_1.tbz http://files.pfsense.org/packages/amd64/8/All/open-vm-tools-nox11-313025_1.tbz
vs
Package manager: Open-VM-Tools 217847

…though that could be a typo.

Jason.

[jimp]

Try updating again shortly, I bumped it up to a newer revision of the package (_2 instead of _1). The new binary was uploaded a while ago but wasn't updated in the xml.

[regis]

I just installed a brand new VM with 2.0-RC1 (i386) built on Thu Mar 17 07:55:22 EDT 2011 and added open-VM-tools :

Downloading http://files.pfsense.org/packages/8/All/open-vm-tools-nox11-313025_2.tbz …  (extracting)
Downloading http://files.pfsense.org/packages/8/All/fusefs-kmod-0.3.9.p1.20080208_7.tbz ...  (extracting)
Downloading http://files.pfsense.org/packages/8/All/pkg-config-0.25_1.tbz ...  (extracting)
Downloading http://files.pfsense.org/packages/8/All/fusefs-libs-2.7.4.tbz ...  (extracting)Loading package configuration... done.
Configuring package components...
Additional files... done.
Loading package instructions...
Custom commands...
Executing custom_php_install_command()...done.
Writing configuration... done.

Installation completed.   Please check to make sure that the package is configured from the respective menu then start the package.

The old version was installing far more dependancies (python26, pear,...) is this OK ?

On the console i see the message "VMware memory control driver initialized"

but in the system logs i see this "root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: failed to start vmware_guestd"

In the vsphere client, vmware tools are marked "not installed"

edit : if i try a /usr/local/etc/rc.d/vmware-guestd.sh start from the console it fails :

Starting vmware_guestd.
/libexec/ld-elf.so.1: Shared object "libgmodule-2.0.so.0" not found, required by "vmtoolsd"

/usr/local/etc/rc.d/vmware-guestd.sh: WARNING: failed to start vmware_guestd

edit2 : I tried to install glib20 (which I think brings libgmodule-2.0.so.0) but it needs python26, perl and pcre

so I installed them but I ran into another problem :

pkg_add glib20.tbz
pkg_add: warning: package 'glib-2.24.1_1' requires 'pkg-config-0.23_1', but 'pkg-config-0.25_1' is installed
pkg_add: warning: package 'glib-2.24.1_1' requires 'gettext-0.18_1', but 'gettext-0.18.1.1' is installed

[Clouseau]

So,is there any hope/idea to get working Open-VM-Tools to 32bit pfSense  ? At 64bit pfSense 2.0 RC1 it works.

Just updated to 2.0-RC1 (i386) built on Sun Mar 20 18:27:34 EDT 2011

Now I have this error:
root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: failed to start vmware_guestd

So Open-VM-Tools are totally broken!

[focalguy]

I updated mine over the weekend (both the RC1 build and Open-VM tools) and it is now not working at all either. I don't know the exact version I had previously that worked so I know that's not much help.

[photonman]

what is the purpose of vm-tools on this type of VM?

Is it really necessary to have installed???

[Sloth]

@photonman:

what is the purpose of vm-tools on this type of VM?

Is it really necessary to have installed???

No not necessary but, imho, recommended if you are planning to run pfSense on a 'production' ESX server hosting other VMs. The vm-tools provide: improved ESX host memory management; improved network performance including some hardware offload (if you can get the vmxnet2 driver to work….....); and allow the ESX host to initiate graceful shutdown of the pfSense guest.

Jason.

[Sloth]

32bit open-vm-tools still not working for me. Just tried a package reinstall on a '2.0-RC1 (i386)
built on Thu Mar 17 07:55:22 EDT 2011' VM, and get the following error:
root: /usr/local/etc/rc.d/vmware-guestd.sh: WARNING: failed to start vmware_guestd

open-vm-tools is still showing as version 217847 in package manager.

NB: I also tried adding a vmxnet2 NIC and, even though the driver looks to initialize OK, it does not pass any traffic. I have to say that I have not had any sucess with the VMXNET2 driver in any build of pfSense 2.0 - anyone else managed to get this to work?

Jason.

[Clouseau]

Still broken: 2.0-RC1 (i386) built on Tue Mar 22 05:44:21 EDT 2011

???

Open-VM-Tools package ver: 217847  - Any news about this?