VMware installation is successful, but VMware fails to launch

English Virtualization
1

Hello Everyone! I am new to OpenSUSE and new to the forum so please excuse my newbieness :stuck_out_tongue:

I am coming from Fedora where i have been using VMware workstation without issues. but when i installed VMware on Tumbleweed i was unable to launch the application. Icon shows up in panel, but then disappears after a second.

I Downloaded the .bundle from broadcom,
chmod +x VMware-Workstation-Full-25H2u1-25219725.x86_64.bundle,
sudo ./VMware-Workstation-Full-25H2u1-25219725.x86_64.bundle to install
And as i have seen several people on this forum encounter i got a promt:
System service scripts directory (commonly /etc/init.d). [/etc/init.d]:

I have tried installing kernel-source kernel-devel, and gcc as described here:

I have tried entering /etc/systemd/system instead of /etc/init.d in the promt

One thing i notice is that no matter what path i write in the system service scripts promt on the install, when i go to the directory to check it is always empty (also no hidden files) it doesnt look like the installer puts anything in the directory

I also do not get any error messages. This is the output from the installer:
sudo ./VMware-Workstation-Full-25H2u1-25219725.x86_64.bundle
Extracting VMware Installer…done.
System service scripts directory (commonly /etc/init.d).: /etc/init.d

Installing VMware Installer 3.1.0
Copying files…
Configuring…
Installing VMware Player Setup 25.0.1
Copying files…
Configuring…
Installing VMware USB Arbitrator 20.11.0
Copying files…
Configuring…
Installing VMware Network Editor 25.0.1
Copying files…
Configuring…
Installing VMware VMX 25.0.1
Copying files…
Configuring…
Installing VMware Tools for Windows Vista or later 13.0.10
Copying files…
Configuring…
Installing VMware Player Application 25.0.1
Copying files…
Configuring…
Installing VMware OVF Tool component for Linux 5.0.0
Copying files…
Configuring…
Installing VMware Network Editor User Interface 25.0.1
Copying files…
Configuring…
Installing VMware VIX Core Library 1.17.0
Copying files…
Configuring…
Installing VMware VIX Workstation-17.0.0 Library 1.17.0
Copying files…
Configuring…
Installing VMware VProbes component for Linux 25.0.1
Copying files…
Configuring…
Installing VMware Workstation 25.0.1
Copying files…
Configuring…
Installation was successful.

i have also tried with version 25H2 just in case there was something wrong with version 25H2u1

Any advice for how i can get VMware working is greatly appreciated :slight_smile:

2

lol, VMWare still uses init scripts? That’s not going to work.

SystemD removed the ability to run init scripts in version 260. Tumbleweed updated to 260.1 in snapshot 20260425. /etc/systemd/system is not, in any way, comparable to /etc/init.d

3

Do not use it with Tumbleweed but VMware-Workstation-Full-25H2-24995812 running on Leap 16.0 here is installing this unit file:

> systemctl cat vmware
# /usr/lib/systemd/system/vmware.service
#
# systemd unit file for VMware Workstation kernel modules and virtual
# networking components.
# .
# Copyright (c) 2022 VMware, Inc.  All rights reserved.
#

[Unit]
Description=VMware host virtualization and network services for Workstation
Before=multi-user.target
After=network.target
Wants=network.target

[Install]
WantedBy=multi-user.target

[Service]
Type=forking
RemainAfterExit=yes
GuessMainPID=no
IgnoreSIGPIPE=no
ExecStart=/usr/lib/vmware/scripts/init/vmware start
ExecStop=/usr/lib/vmware/scripts/init/vmware stop

and a sym link in /etc/init.d

> ls -l  /etc/init.d/vmware 
lrwxrwxrwx. 1 root root 35 19. Okt 2025  /etc/init.d/vmware -> /usr/lib/vmware/scripts/init/vmware

but this link is not used at least on Leap 16.0. You must disable secure boot if active or sign the VMware kernel modules with your own keys otherwise they do not load.

4

I get the same output when running systemctl cat vmware

I added the symlink and tried again, but the issue persists…

I have secure boot disabled

Now i ran systemctl status vmware and got this:

systemctl status vmware.service
× vmware.service - VMware host virtualization and network services for Workstation
     Loaded: loaded (/usr/lib/systemd/system/vmware.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2026-04-30 21:23:00 CEST; 13s ago
 Invocation: f06081fdca344b9ba004f1386bb82145
    Process: 3671 ExecStart=/usr/lib/vmware/scripts/init/vmware start (code=exited, status=1/FAILURE)
        CPU: 53ms

It says its failed with exit code, i am not very familiar with systemd outside the basic status, start, restart, enable etc. so i will have a look around the internet to see if i find some information from this output

5

journalctl -xeu vmware

6 
journalctl -xeu vmware
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
-- No entries --
7

I run VMware Workstation 25h2u1 on Tumbleweed here with Secure Boot disabled.

The systemd unit file that @rawar is using is identical to the unit file I have on my system, and it works fine here.

Let’s see what the log output is - but I can confirm that it works fine here. Make sure you run journalctl as root or use sudo.

ETA: What kernel are you running?

8

Ahh sudo helps

sudo journalctl -xeu vmware
[sudo] password for root:
░░ The job identifier is 4281.

Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
An ExecStart= process belonging to unit vmware.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
Subject: A start job for unit vmware.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit vmware.service has finished with a failure.
The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
Subject: Unit process exited
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
An ExecStart= process belonging to unit vmware.service has exited.
The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
Subject: A start job for unit vmware.service has failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.
lines 44-72/72 (END)
░░ The job identifier is 4281.
Apr 30 21:23:00 suse vmware[3671]: Starting VMware services:
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine monitor - failed
Apr 30 21:23:00 suse vmware[3671]:    Virtual machine communication interface - done
Apr 30 21:23:00 suse vmware[3671]:    VM communication interface socket family - done
Apr 30 21:23:00 suse vmware[3671]:    Virtual ethernet - failed
Apr 30 21:23:00 suse vmware[3671]:    VMware Authentication Daemon - done
Apr 30 21:23:00 suse systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit vmware.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Apr 30 21:23:00 suse systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Apr 30 21:23:00 suse systemd[1]: Failed to start VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 4281 and the job result is failed.

I had to remove some of the earlier part of journalctl as the maximum character limit on the forum was reached
my kernel version is 6.19.12-1-default

9

Check the output of lsmod | grep vm and look for vmnet, vmw_vsock_vmci_transport, vmw_vmci, and vmmon. Those modules need to be loaded or the service won’t start.

If they’re not present, try running (as root):

vmware-modconfig --console --install-all

You will probably get a message saying that GLib does not have GSettings support., but the modules will build. If they don’t, you need to make sure you have the kernel development pattern installed.

10

They now include a systemd unit file that runs the init scripts, so no init.d support is needed any more (finally).

11

Output:

lsmod | grep vm
vmw_vsock_vmci_transport    49152  0
vsock                  69632  1 vmw_vsock_vmci_transport
vmw_vmci              110592  1 vmw_vsock_vmci_transport
kvm_amd               253952  0
kvm                  1441792  1 kvm_amd
irqbypass              16384  1 kvm
ccp                   208896  1 kvm_amd

vmnet and vmmon are missing

ran as root user:

vmware-modconfig --console --install-all
[AppLoader] GLib does not have GSettings support.

(process:7820): GLib-CRITICAL **: 22:27:44.530: g_file_test: assertion 'filename != NULL' failed
Failed to setup build environment: Header path "(null)" is not a valid directory.
12

Yes, vmmon and vmnet are missing, and that is likely what the issue is.

It looks like you lack the kernel development pattern.

Run zypper in --type pattern devel_kernel. Once that’s done, then rerun the vmware-modconfig command and it should build the modules.

13

I did lack the kernel development pattern, unfortunately vmware-modconfig still fails

sudo zypper in --type pattern devel_kernel
[sudo] password for root:
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 23 recommended packages were automatically selected:
  binutils-devel cyrus-sasl-devel diffstat e2fsprogs-devel ed gcc-info git git-email glibc-info gmp-devel indent
  libaio-devel libdb-4_8-devel libosip2-devel libstdc++-devel makeinfo-lang openldap2-devel pam-devel patchutils
  perl-Archive-Zip quilt sparse subversion

The following 59 NEW packages are going to be installed:
  autoconf automake binutils-devel cyrus-sasl-devel diffstat e2fsprogs-devel ed gcc15-info gcc-info gdbm-devel git
  git-email git-svn glibc-info gmp-devel indent libaio-devel libapr1-0 libapr-util1-0 libblkid-devel libcom_err-devel
  libdb-4_8-devel libeconf-devel libext2fs-devel libgmpxx4 libncurses_c++6 libosip2-15 libosip2-devel libserf-1-1
  libstdc++-devel libsvn_auth_kwallet-1-0 libtool libuuid-devel makeinfo makeinfo-lang ncurses-devel openldap2-devel
  pam-devel patchutils patterns-base-basesystem patterns-devel-base-devel_basis patterns-devel-base-devel_kernel
  perl-Archive-Zip perl-Authen-SASL perl-Crypt-URandom perl-Digest-HMAC perl-Error perl-Git perl-IO-Socket-SSL
  perl-MailTools perl-Net-SMTP-SSL perl-Net-SSLeay perl-TimeDate quilt sparse subversion subversion-bash-completion
  subversion-perl tack

The following 3 NEW patterns are going to be installed:
  basesystem devel_basis devel_kernel

59 new packages to install.

Package download size:    39.6 MiB

Package install size change:
              |     128.1 MiB  required by packages that will be installed
   128.1 MiB  |  -      0 B    released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y

  -- **Removed for ease of reading**

.......................................[done]
Running post-transaction scripts ................................................................................[done]

~ took 19s
❯ sudo vmware-modconfig --console --install-all
[AppLoader] GLib does not have GSettings support.

(process:9175): GLib-CRITICAL **: 22:36:03.224: g_file_test: assertion 'filename != NULL' failed
Failed to setup build environment: Header path "(null)" is not a valid directory.
14

Looks like kernel-source isn’t part of the pattern. Try installing that as well as kernel-default-devel which is also missing.

15

kernel-source is already installed:

sudo zypper in kernel-source
[sudo] password for root:
Loading repository data...
Reading installed packages...
'kernel-source' is already installed.
No update candidate for 'kernel-source-7.0.1-1.1.noarch'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
16

That shows the kernel as 7.0.1, not the version 6.19.12 that you said you’re running. You need to match the versions.

17

I would not expect the vmware modules to compile against a 7.x kernel yet, as there are likely ABI changes.

18

Ok, then i will get the 6.19.12 version and try again. i dont know why zypper installed 7.0.1

uname -r
6.19.12-1-default
1 Like
19

Perhaps?

20

I haven’t had a need to use that, the modules still build even with that message showing up.