Project

General

Profile

Actions
Copy link

Bug #4491

closed

Incorrect module location in start up script for Open-VM-Tools

Added by Toni Garcia about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
open-vm-tools
Target version:
-
Start date:
03/06/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.2
Affected Plus Version:
Affected Architecture:

Description

After upgrade from 2.1.5 to 2.2 and reinstall open-vm-tools package I realize that open-vm-tools kernel modules were not loading:

[2.2-RELEASE][root@pfsense]/usr/pbi: kldstat
Id Refs Address Size Name
1 10 0xffffffff80200000 22c57e8 kernel

The problem is that start up script /usr/local/etc/rc.d/vmware-kmod.sh tries to load kernel modules from /usr/local/lib/vmware-tools/modules/drivers/, where these are linked to the real package directory /usr/pbi/open-vm-tools-nox11-amd64/lib/vmware-tools/modules/drivers.

[2.2-RELEASE][root@pfsense]/root: ls -lrt /usr/local/lib/vmware-tools/modules/drivers/
total 0
lrwxr-xr-x  1 root  wheel  77 Jan  9 16:22 vmxnet.ko -> /usr/pbi/open-vm-tools-nox11-amd64/lib/vmware-tools/modules/drivers/vmxnet.ko
lrwxr-xr-x  1 root  wheel  79 Jan  9 16:22 vmmemctl.ko -> /usr/pbi/open-vm-tools-nox11-amd64/lib/vmware-tools/modules/drivers/vmmemctl.ko
lrwxr-xr-x  1 root  wheel  77 Jan  9 16:22 vmhgfs.ko -> /usr/pbi/open-vm-tools-nox11-amd64/lib/vmware-tools/modules/drivers/vmhgfs.ko
lrwxr-xr-x  1 root  wheel  78 Jan  9 16:22 vmblock.ko -> /usr/pbi/open-vm-tools-nox11-amd64/lib/vmware-tools/modules/drivers/vmblock.ko
lrwxr-xr-x  1 root  wheel  80 Jan  9 16:22 linker.hints -> /usr/pbi/open-vm-tools-nox11-amd64/lib/vmware-tools/modules/drivers/linker.hints

However, thsi location doesn't contain actually the modules, so the package prefix is incorrect:

[2.2-RELEASE][root@pfsense]/root: pbi_info -v open-vm-tools-1280544_9-amd64
PBI Information for: open-vm-tools-1280544_9-amd64
-----------------------------------------------------
Name: open-vm-tools
InstalledBy: root
RootInstall: YES
Version: 1280544_9
Built: 20141127 224032
Prefix: /usr/pbi/open-vm-tools-amd64
Author: swills@FreeBSD.org
Website: http://open-vm-tools.sourceforge.net
Arch: amd64
FbsdVer: 10.0-STABLE
CreatorVer: 1.0
ArchiveCount: 10013
ArchiveSum: 6ce8ce1af97f35fceff5f46bd829d9440f7b050453343f81fabd5ed39fc0b86f
Signature: Verified
License: LGPL21
AutoUpdate: NO

My workaround has been to make a symlink in /usr/pbi, from /usr/pbi/open-vm-tools-nox11-amd64 to /usr/pbi/open-vm-tools-amd64. After that and executing the start up script, modules are loaded as expected.

I think the real solution is to correct the location for modules in start up scripts.

Actions
Copy link
 #1

Updated by Toni Garcia about 9 years ago

Found the following line:

<depends_on_package_pbi>open-vm-tools-1280544_9-##ARCH##.pbi</depends_on_package_pbi>

in https://github.com/pfsense/pfsense-packages/blob/master/pkg_config.10.xml

It seems to me that the package must be something like:

<depends_on_package_pbi>open-vm-tools-nox11-1280544_4-##ARCH##.pbi</depends_on_package_pbi>
Actions
Copy link
 #2

Updated by Chris Buechler about 9 years ago

  • Status changed from New to Resolved

fixed (by removing the modules entirely for now at least, they mostly aren't necessary, and cause stability issues)

Actions
Copy link

Also available in: Atom PDF