Open-VM-Tools install fails

fbearoff

Hi,

I've been running pfsense 2.2 under ESXi 5.5 through the beta and RC period. I've decided to do a fresh install of the final version and am having trouble getting open-vm-tools installed. This is what I get when installing through the GUI:

Beginning package installation for Open-VM-Tools .
Downloading package configuration file… done.
Saving updated package information... done.
Downloading Open-VM-Tools and its dependencies...
Checking for package installation...
Downloading https://files.pfsense.org/packages/10/All/open-vm-tools-1280544_9-amd64.pbi ... (extracting)
Verifying Checksum...SKIP_ARCHLINES: 67
Archive checksum: f0f79c73b63cd6549de292e7dd4fdec8387df9136518268fb299089d0d309e5b
Saved checksum: 6ce8ce1af97f35fceff5f46bd829d9440f7b050453343f81fabd5ed39fc0b86f
ERROR: /tmp/apkg_open-vm-tools-1280544_9-amd64.pbi failed checksum, the archive may be corrupt.
of open-vm-tools-1280544_9-amd64 failed!

Installation aborted.Removing package...
Starting package deletion for open-vm-tools-1280544_9-amd64...done.
Removing Open-VM-Tools components...
Loading package instructions...
Include file open-vm-tools.inc could not be found for inclusion.
Deinstall commands...
Not executing custom deinstall hook because an include is missing.
Removing package instructions...done.
Auxiliary files... done.
Package XML... done.
Configuration... done.
done.
Failed to install package.

Installation halted.

I've enabled the option under Advanced>Miscellaneous to ignore checksum errors in package installs which results in the same error. I've attempted manual install through the shell according to these instructions https://forum.pfsense.org/index.php?topic=75430.0, this allows the package to install through the GUI, but upon checking if the VM tools are running according to https://doc.pfsense.org/index.php/Open_VM_Tools_package, I get only the following result from ps uxawww | grep vmware

root 99525 0.0 0.1 17144 2648 - S 12:13PM 0:00.00 sh -c ps uxawww | grep vmware 2>&1
root 99872 0.0 0.0 552 464 - R 12:13PM 0:00.00 grep vmware

and

Id Refs Address Size Name
1 1 0xffffffff80200000 22c57e8 kernel

from kldstat meaning the tools are not running. Anyone else have similar issues?

wiz561

I just posted a problem with this a few seconds ago. :) I'm having problems with the package as well, but not when it installs. It installs fine for me, but when it boots, I get errors… Here's the message I posted...

Hi!

I just updated to 2.2 this-morning and noticed that I'm getting errors when the box boots up. In my dmesg, I have the following...

KLD vmmemctl.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmxnet.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmblock.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmhgfs.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
em0: promiscuous mode enabled
em1: promiscuous mode enabled
KLD vmmemctl.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmxnet.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmblock.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmhgfs.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type

I am running esxi on this box, so having the vmware tools available is a plus. Things still work, but I have a feeling that I will run into problems in the future. I've also tried to uninstall/reinstall the package but still get the errors.

Thanks!

neptunus

I also updated to 2.2 this-morning and have the same problems. In my dmesg, I have the following…


KLD vmmemctl.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmxnet.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmblock.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type
KLD vmhgfs.ko: depends on kernel - not available or version mismatch
linker_load_file: Unsupported file type

I am running esxi 5.1 on my server, I would like to have vmware tools running. Installing manualy as mentioned earlier, does also not work unfortunately!

What to do?

marcelloc

Install openvmtools from freebsd ports via pfsense console

pkg install open-vm-tools-nox11

It's a freebsd 10.1 x vmware issue, not related to pfsense itself.

neptunus

@marcelloc:

Install openvmtools from freebsd ports via pfsense console
pkg install open-vm-tools-nox11
It's a freebsd 10.1 x vmware issue, not related to pfsense itself.

It looks like this way of installing is working! Thanks!

fbearoff

@neptunus:

@marcelloc:
Install openvmtools from freebsd ports via pfsense console
pkg install open-vm-tools-nox11
It's a freebsd 10.1 x vmware issue, not related to pfsense itself.
It looks like this way of installing is working! Thanks!

No luck for me, package installs fine but does not load upon reboot after adding the following arguments to /etc/rc.conf as instructed by the package during installation

vmware_guest_vmblock_enable="YES"
vmware_guest_vmhgfs_enable="YES"
vmware_guest_vmmemctl_enable="YES"
vmware_guest_vmxnet_enable="YES"
vmware_guestd_enable="YES"

Did you do anything else to get it working?

marcelloc

What you get if you run vmtools rc.d script on console?

fbearoff

@marcelloc:

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.ko

and 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?

biggsy

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

@biggsy:

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

marcelloc

Rename or symlinks rc.d scripts to .sh and test again.

IIRC, pfsense calls only .sh scripts on boot.

biggsy

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.

wiz561

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!

fbearoff

@wiz561:

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.

marcelloc

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.

wiz561

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.

fbearoff

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 :(