I cannot compile the vmmon and vmnet modules under Tumbleweed. I get the following errors:
[AppLoader] GLib does not have GSettings support.
sh: line 1: /etc/init.d/vmware: No such file or directory
Unable to stop services.
I’ve tried this under plain vanilla VMware Player 17.5.0 and with the modified tarballs that are available on Github that claim to fix problems with newer kernels and get the same errors. Does anyone have any solutions?
I upgraded to VMware Workstation 17.5, and it seemed to compile just fine on the most recent TW kernels.
Using the github modules, what branch did you check out, and what commands did you run? Please put all that info in code tags (identified as </> in the toolbar) to preserve formatting.
Also, what release of TW are you running. Use cat /etc/os-release
and put the output in code tags as well.
Thanks for the reply:
This should answer the github questions:
<wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-17.5.0.tar.gz
tar -xzf workstation-17.5.0
cd vmware-host-modules-workstation-17.5.0
vmware-modconfig --console --install-all>
As for the version:
<NAME=“openSUSE Tumbleweed”
VERSION=“20231026”
ID=“opensuse-tumbleweed”
ID_LIKE=“opensuse suse”
VERSION_ID=“20231026”
PRETTY_NAME=“openSUSE Tumbleweed”
ANSI_COLOR=“0;32”
CPE_NAME=“cpe:/o:opensuse:tumbleweed:20231026”
BUG_REPORT_URL=“https://bugzilla.opensuse.org”
SUPPORT_URL=“https://bugs.opensuse.org”
HOME_URL=“https://www.opensuse.org”
DOCUMENTATION_URL=“Portal:Tumbleweed - openSUSE Wiki”
LOGO=“distributor-logo-Tumbleweed”>
I apologize if the code tags did not work as the choice in the little menu at the top of the edit window wanted to give me preformatted text rather than code tags, so I tried to enter them manually.
Sorry about the confusion with the tags - preformatted is actually just fine.
Looks like the modules you downloaded are correct for Player 17.5 as well - I typically do a git checkout from a branch rather than pulling down the pre-packaged file you did, but either should be fine. Like you, I am using systemd, and /etc/init.d doesn’t even exist on my system.
Do you have vmware startup scripts in /usr/lib/systemd/system
for VMware? I show vmware.service
and vmware-USBArbitrator.service
, and both files’ contents indicate they’re provided by VMware.
But strangely, with Workstation 17.5, I didn’t need to use those modules - the included code with the product seemed to build just fine here.
I’m going to attempt to install VMware Player inside a VM to see if I can duplicate what you’re seeing.
This looks like it’s the source of your issue - after you unpack and change to the vmware-host-modules-workstation-17.5.0 directory, you need to either:
- Run
make
and sudo make install
, which installs the modules, and you don’t need to run vmware-modconfig at all, or
- Run
tar -cf vmmon.tar vmmon-only; tar -cf vmnet.tar vmnet-only; cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/; vmware-modconfig --console --install-all
You seem to have combined the instructions from the two steps, which is attempting to build not using the downloaded code, but instead is using the VMware-provided code, which I confirmed with Player doesn’t work on TW.
That said, with Player 17.5.0, I didn’t need the info from the git repo to run. During installation, it prompted me for the init.d directory, and I just pointed it at my home directory - it continued the installation and installed systemd startup scripts and the vmware-modconfig command didn’t care about /etc/init.d at all.
1 Like
Thank you so much. I used the make and sudo make install method and it worked like a charm.
The make install method did allow me to open Player, but when I attempted to open a virtual machine it told me the modules were not installed. Here is the output from the make install step: install -D -t /lib/modules/6.5.9-1-default/misc vmmon-only/vmmon.ko vmnet-only/vmnet.ko strip --strip-debug /lib/modules/6.5.9-1-default/misc/vmmon.ko /lib/modules/6.5.9-1-default/misc/vmnet.ko if test -z ""; then /sbin/depmod -a 6.5.9-1-default; fi
I assumed they installed. How do I check?
I also tried method number 2 and got the GSettings error.
Sorry, I’m an idiot. I forgot to reboot after the make install step. Everything works fine now.
1 Like