Bug #12085
closedOpenVM Tools vmware-kmod service won't start in 2.5.2 RC on ESXi 6.0
0%
Description
Tetsed with OpenVM Tools version 10.1.0_5,1
Since upgrading to 2.5.2.r.20210626.0300 the vmware-kmod service fails to start with the following system logs:
Jun 26 14:08:28 kernel KLD vmmemctl.ko: depends on kernel - not available or version mismatch
Jun 26 14:08:28 kernel linker_load_file: /usr/local/lib/vmware-tools/modules/drivers/vmmemctl.ko - unsupported file type
Jun 26 14:08:28 kernel KLD vmblock.ko: depends on kernel - not available or version mismatch
Jun 26 14:08:28 kernel linker_load_file: /usr/local/lib/vmware-tools/modules/drivers/vmblock.ko - unsupported file type
Shell Output - ps uxawww | grep vmtoolsd:
root 49344 0.0 0.1 11444 2868 - S 14:14 0:00.00 sh -c ps uxawww | grep vmtoolsd 2>&1
root 49462 0.0 0.1 11260 2504 - S 14:14 0:00.00 grep vmtoolsd
root 69145 0.0 0.3 18788 5708 - S 14:12 0:00.13 /usr/local/bin/vmtoolsd -c /usr/local/share/vmware-tools/tools.conf -p /usr/local/lib/open-vm-tools/plugins/vmsvc
The vmware-guestd service still runs and basic functionality like shutting down the system from ESXi is still working. Both services were running well on the June 17th build.
Updated by Max Leighton over 3 years ago
- Subject changed from OpenVM Tools vmware-kmod service won't start in 2.5.2 RC to OpenVM Tools vmware-kmod service won't start in 2.5.2 RC on ESXi 6.0
Updated by Christian McDonald over 3 years ago
Kris saw smiliar (if not the same) errors related to the WireGuard kernel module recently. Might check with Renato.
Updated by Max Leighton over 3 years ago
Now I can't reproduce this on 2.5.2.r.20210629.1350. The service starts/restarts without issues on upgraded systems so it appears to have been fixed in the latest build
Updated by Renato Botelho over 3 years ago
- Status changed from New to Resolved
- Assignee set to Renato Botelho
- Target version set to 2.5.2
Yeah, since we moved FreeBSD src to an earlier version to remove some pf changes that was causing issues, it rebuilt all kmods using same version and it was not reinstalled. I've bumped package release so upgrade code finds it and reinstall.