Open-VM-Tools install fails
-
What you get if you run vmtools rc.d script on console?
-
What you get if you run vmtools rc.d script on console?
If I manually start the 2 scripts in /usr/local/etc/rc.d/ (vmware-guestd and vmware-kmod) I get from kldstat
Id Refs Address Size Name
1 10 0xffffffff80200000 22c57e8 kernel
2 1 0xffffffff82611000 2198 vmmemctl.ko
3 1 0xffffffff82614000 23d8 vmxnet.ko
4 1 0xffffffff82617000 2bf0 vmblock.ko
5 1 0xffffffff8261a000 81b4 vmhgfs.koand from ps uxawww | grep vmware
root 9150 0.0 1.6 98804 33004 - S 8:33PM 0:00.14 /usr/local/bin/vmtoolsd -c /usr/local/share/vmware-tools/tools.conf -p /usr/local/lib/open-vm-tools/plugins/vmsvc
ESXi is also reporting that 3rd party VMware tools are installed and running. So how do we get this starting at boot?
-
fbearoff,
When you have successfully started the tools manually, are you able to shutdown the pfSense VM from the viClient or do you get an error?
-
fbearoff,
When you have successfully started the tools manually, are you able to shutdown the pfSense VM from the viClient or do you get an error?
I've been getting errors and the VM doesn't want to shutdown or restart when initiated from ESXi. I get this message from ESXi "vix error code = 1" and "VMware memory control driver initialized" at the pfsense console
-
Rename or symlinks rc.d scripts to .sh and test again.
IIRC, pfsense calls only .sh scripts on boot.
-
Thanks fbearoff, same error as I'm getting. Maybe what vfrontde is seeing as well.
Thanks to you as well marcelloc - for the advice and all your hard work on packages.
-
Will the pfsense package for open-vmtools be updated soon, or will this freebsd pkg install be the way to install it in the future? I don't want to mess much with my install so if the package updates soon, I'm just going to let things be.
Thanks!
-
Will the pfsense package for open-vmtools be updated soon, or will this freebsd pkg install be the way to install it in the future? I don't want to mess much with my install so if the package updates soon, I'm just going to let things be.
Thanks!
Hoping for an official update as well, as of right now none of these suggestions have resulted in working vm-tools for me.
-
This package I prefer to install via pkg ng. Pbi is something that needs a lot of work to compile and Symlink to do not get missing libs.
I'll try a 2.2 Release on vmware 5.5 and see what happens.
-
It's been a few days and was just wondering if anybody had any updates.
Also, it's a long shot, but can not installing the vmware tools cause goofiness with my WAN nic? I'm 99% positive that the fault is with comcast. Since the 2.2 upgrade and my packet loss and long icmp return times, I just thought I'd ask.
-
No luck with anything, doesn't look like it is a high priority for the devs, there hasn't been any code changes on the git repository for this package :(
