Open-VM-Tools don't work well any more on pfsense 2.2+
-
your clearly not installing the correct tools.. your just installing the package from package installs right or are you trying to install with pkg install? Or a file?
That error is something wrong - what version of pfsense are you running, and what version of esxi?
Im going to do a clean install of 2.2.2 and install the openvm package because you should not be having these problems.
edit: Well I can see why you might be having problems
On a clean install of 2.2.2 64bit and trying to install the openvm tools package it just seems to hang onExecuting custom_php_install_command()…
And yup its still actually downloading _9 vs the package saying its _11, let me give it a bit more time and see if it every finishes, etc.
-
pfSense 2.2.2 and ESXi 4.1U3 at test site.
I click install on the Open VM package available in the packages menu.
-
I don't think freebsd 10.1 is supported on esxi 4.. Pretty sure 10.1 was not available until 5.5u2 – did they back port to 4??
http://blogs.vmware.com/guestosguide/guest-os/unix-and-others/freebsd
-
Its just installed as FreeBSD 64bit. No specific choice of OS.
Works fine and runs no issues. I just get the error in the Open Vmtools package.
-
dude 10.1 is not supported on that version of esxi, it works your lucky.. Run a older version of pfsense if your not going to be current with your esxi version
also see this error other than _9 being downloaded vs _11
php-fpm[77198]: /pkg_mgr_install.php: Could not open /usr/local/share/vmware-tools/tools.conf for writingIf you create the dir and file the pkg installs, shows 3rd party and running in esxi, but the ko's are not loaded when you check kldstat
Clearly the package is broken and will have to wait until its fixed. But again freebsd 10.1 and pfsense 2.2 is not supported on that version of esxi
-
2.1.5 vs 2.2.2.
Opne Vmtools installed on both systems. Same version of ESXi. Serving the pfsense clusters.
I have attached screendumps.
Error began with upgrade to 2.2.2…. 2.1.5 running no issues at all. Open Vm tools shows unmanaged in 2.1.5 and ESXi 4.1U3.
-
Error began with upgrade to 2.2.2…. 2.1.5 running no issues at all. Open Vm tools shows unmanaged in 2.1.5 and ESXi 4.1U3.
Yeah. When you take modules compiled for FreeBSD 8.3 kernel and shove them on FreeBSD 10.1 box, things don't work. Hardly surprising. The errors are damn explicit, cannot believe that totally broken packages are shipped. (Now, at least the breakage resulting from install seems to be mitigated by the fact that it's so badly broken that it actually fails to install altogether, which is a good thing, considering the state of things… ::))
-
Yes.
But its seems they have corrected the vmxnet.ko file error.
-
But its seems they have corrected the vmxnet.ko file error.
Yeah. By removing the module altogether.
-
Guess ill wait this the package is fixed.
-
Apparently the driver is present in 10.1 so its not needed in the tools??
But its seems they have corrected the vmxnet.ko file error.
Yeah. By removing the module altogether.
-
freebsd 10.1 has native vmx3 support so you don't need the tools at all really other than to be able to clearly shutdown pfsense from esxi, integration with the console, etc.
I reported that is fully broken in the package thread.. Not sure on who the specific package owner/contributors are - but sure they will fix it up soon enough.
You can run pfsense 2.2.2 just fine on above 5.5u2 of esxi without any issues, and since vmx3 is part of freebsd now you don't really need to install the tools.
-
Every open issue that existed for open-vm-tools is fixed now.
-
TOTALLY AWESOME!!
Thanks Chris. Really appreciated!
-
Gonna have a go on ESXI 5.5U2 and 6 ASAP.
-
Still cant run a custom shutdown script.
Running this custom script.
#!/usr/local/bin/php -f
/* parse the configuration and include all functions used below */
require_once("config.inc");
require_once("functions.inc");
system_halt();
?>Dunno if vmware-tools can even run this script.
Any ideas?
-
Is there a need for a shutdown script? It shuts down the VM without one.
Did you chmod +x that php file?
-
Yes i need to run a custom script. I'm running CP+FreeRADIUS with SQL accounting, when i shutdown the VM no acctstoptime it send to the SQL database. And since im use Simultaneouse-Use attribute this is a problem. This problem does not occur when u shutdown/reboot pfsense from the GUI.
Yeah the file is executable. Running it from the commandline works fine.
Maby i should write a script to query the database for empty acctstoptime and run it with shellcmd @ boot.
-
How does that error point to problem with the script? With the tools package installed and no script can you shutdown pfsense vm?
Do you have the path correctly to where the script in the tools?
-
Yes shutdown works if i disable the shutdown script.
Path is correct.
