VMWare Service won't run on Fedora 35?

afiadi · May 6, 2022, 3:31pm

Hai All,
I’ve succesfully install vmware workstation in Fedora 35, I use the lastest version of vmware workstaion. But, when check the status of vmware service, I got this error message:

 systemctl status vmware.service
× vmware.service - SYSV: This service starts and stops VMware services
     Loaded: loaded (/etc/rc.d/init.d/vmware; generated)
     Active: failed (Result: exit-code) since Fri 2022-05-06 22:10:41 WIB; 14s ago
       Docs: man:systemd-sysv-generator(8)
    Process: 5914 ExecStart=/etc/rc.d/init.d/vmware start (code=exited, status=1/FAILURE)
      Tasks: 1 (limit: 3988)
     Memory: 3.9M
        CPU: 314ms
     CGroup: /system.slice/vmware.service
             └─869 /usr/sbin/vmware-authdlauncher

Mei 06 22:10:41 192.168.1.8 vmware[5914]:    VM communication interface socket family[  OK  ]
Mei 06 22:10:41 192.168.1.8 vmware[5914]:    Virtual ethernet[GAGAL]
Mei 06 22:10:41 192.168.1.8 vmware[5914]:    VMware Authentication Daemon[  OK  ]
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Control process exited, code=exited, status=1/FAILURE
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Failed with result 'exit-code'.
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 869 (vmware-authdlau) remains running afte>
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 5953 (bash) remains running after unit sto>
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 5954 (logger) remains running after unit s>
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 5955 (vmware-authdlau) remains running aft>
Mei 06 22:10:41 192.168.1.8 systemd[1]: Failed to start SYSV: This service starts and stops VMware services.

vmware version:

vmware --version
VMware Workstation 16.2.3 build-19376536

I use the lastest kernel version:

uname -r
5.17.5-200.fc35.x86_64

And I successfully compile module vmmon and vmnet from vmware-host-modules

make
make -C vmmon-only 
make[1]: Memasuki direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only'
Using kernel build system.
make -C /lib/modules/5.17.5-200.fc35.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[2]: Memasuki direktori '/usr/src/kernels/5.17.5-200.fc35.x86_64'
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/linux/driver.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/linux/driverLog.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/linux/hostif.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/apic.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/comport.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/cpuid.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/crosspage.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/memtrack.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/moduleloop.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/phystrack.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/sharedAreaVmmon.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/statVarsVmmon.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/task.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/common/vmx86.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/bootstrap/bootstrap.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/bootstrap/monLoader.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/bootstrap/monLoaderVmmon.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/bootstrap/vmmblob.o
  LD [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/vmmon.o
  MODPOST /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/Module.symvers
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/vmmon.mod.o
  LD [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/vmmon.ko
  BTF [M] /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/vmmon.ko
Skipping BTF generation for /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only/vmmon.ko due to unavailability of vmlinux
make[2]: Meninggalkan direktori '/usr/src/kernels/5.17.5-200.fc35.x86_64'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[2]: Memasuki direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only'
make[2]: 'postbuild' sudah baru.
make[2]: Meninggalkan direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make[1]: Meninggalkan direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmmon-only'
make -C vmnet-only 
make[1]: Memasuki direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only'
Using kernel build system.
make -C /lib/modules/5.17.5-200.fc35.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[2]: Memasuki direktori '/usr/src/kernels/5.17.5-200.fc35.x86_64'
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/driver.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/hub.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/userif.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/netif.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/bridge.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/procfs.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/smac_compat.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/smac.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vnetEvent.o
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vnetUserListener.o
  LD [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vmnet.o
  MODPOST /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/Module.symvers
  CC [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vmnet.mod.o
  LD [M]  /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vmnet.ko
  BTF [M] /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vmnet.ko
Skipping BTF generation for /home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only/vmnet.ko due to unavailability of vmlinux
make[2]: Meninggalkan direktori '/usr/src/kernels/5.17.5-200.fc35.x86_64'
make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[2]: Memasuki direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only'
make[2]: 'postbuild' sudah baru.
make[2]: Meninggalkan direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make[1]: Meninggalkan direktori '/home/afiadi/Unduhan/VMWare-Workstation/vmware-host-modules/vmnet-only'

sudo make install
install -D -t /lib/modules/5.17.5-200.fc35.x86_64/misc vmmon-only/vmmon.ko vmnet-only/vmnet.ko
strip --strip-debug /lib/modules/5.17.5-200.fc35.x86_64/misc/vmmon.ko /lib/modules/5.17.5-200.fc35.x86_64/misc/vmnet.ko
if test -z ""; then /sbin/depmod -a 5.17.5-200.fc35.x86_64; fi

I also check this vmware service is the one only service failed on boot

systemctl list-units --state=failed
  UNIT           LOAD   ACTIVE SUB    DESCRIPTION                                        
● vmware.service loaded failed failed SYSV: This service starts and stops VMware services

but vmmon and vmnet successfully installed

vmware-modconfig --console --install-status
[AppLoader] GLib does not have GSettings support.
vmmon: installed
vmnet: installed

This is the result from journalctl -xeu

sudo journalctl -xeu vmware.service
░░ 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.
Mei 06 22:10:41 192.168.1.8 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'.
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 869 (vmware-authdlau) remains running afte>
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 5953 (bash) remains running after unit sto>
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 5954 (logger) remains running after unit s>
Mei 06 22:10:41 192.168.1.8 systemd[1]: vmware.service: Unit process 5955 (vmware-authdlau) remains running aft>
Mei 06 22:10:41 192.168.1.8 systemd[1]: Failed to start SYSV: This service starts and stops VMware services.
░░ 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 4209 and the job result is failed.

But very weird in my another laptop, I also installed VMware workstation the lastest version in Fedora Scientific Lab with DE KDE Plasma, use the same kernel and Fedora version(35) and it works flawlessly and normally.
I’ve searched the solution on the internet but this problem still doesn’t solved.
How to solved this problem?

Thank You in Advance.

ilikelinux · May 6, 2022, 4:19pm

Please check in the boot-log if an app before or after has errors.
sudo sed $'s/\^\[/\E/g' /var/log/boot.log

You can compare with the other Laptop you have what’s different.

afiadi · May 6, 2022, 4:23pm

This is in my another laptop vmware service is running normally. With the same lastest kernel, the same fedora version and the same vmware version,

Why the behaviour is different?

Thank You in Advance

afiadi · May 6, 2022, 4:28pm

I tried your sugestion, the result is the same with command in my main thread above systemctl list-units --state=failed
All others service is running normally and properly

afiadi · May 6, 2022, 4:35pm

I’ve compared with my another laptop the result is the same for Failed to start SysV, but vmware service is running normally. Why the same error service but different result for vmware service?

TIA

ledeni · May 6, 2022, 6:33pm

Did you disable secure boot on this system ? If not just disable it and try like that to run VMWare.service.

computersavvy · May 6, 2022, 7:38pm

You know, when someone says ‘these two systems are the same’ one tends to assume they know the details.

Only by digging can one tell what tiny detail is different.

You might try booting the system that fails to start vmware then run dmesg | grep -iE 'secure|vmmon' to see what that might tell you about loading those kernel modules. Running the same command on both systems will allow you to see the differences as well.

The comment by @ledeni could be the answer.

afiadi · May 7, 2022, 7:49am

I installed fedora 35 with secure boot disabled, but how this feature is enabled in my bios? I’ve dual boot installed in this laptop with windows 10. After I reading this I check my bios, yes secure boot is enabled, I disabled it and boot to fedora and now is working normally. Thank you to remain me about that, because I sure secure boot is disabled when I installed Fedora 35.