Problem with VMWare Workstation Pro in Fedora 39

josys36 · March 11, 2024, 5:34pm

I was running VMWare Workstation Pro on my Lenovo P50 workstation with Fedora 38 without a problem. When I converted to a System76 desktop I started having issues with the virtual networks in VMWare. My VMs had no networking. After I switched to Kubuntu this issue went away. I’ve since installed Fedora 39 and the same issue persists.

Here is the output of trying to build the VM modules.

Updating VMWare Modules...
[AppLoader] GLib does not have GSettings support.
make: Entering directory '/tmp/modconfig-FQapFz/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.7.7-200.fc39.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/kernels/6.7.7-200.fc39.x86_64'
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/linux/hostif.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/apic.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/comport.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/cpuid.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/crosspage.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/memtrack.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/moduleloop.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/phystrack.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/sharedAreaVmmon.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/statVarsVmmon.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/task.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/common/vmx86.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/bootstrap/bootstrap.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/bootstrap/monLoader.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/bootstrap/monLoaderVmmon.o
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/bootstrap/vmmblob.o
  LD [M]  /tmp/modconfig-FQapFz/vmmon-only/vmmon.o
/tmp/modconfig-FQapFz/vmmon-only/vmmon.o: warning: objtool: CrossPage_CodePage+0x207: 'naked' return found in RETHUNK build
  MODPOST /tmp/modconfig-FQapFz/vmmon-only/Module.symvers
  CC [M]  /tmp/modconfig-FQapFz/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/modconfig-FQapFz/vmmon-only/vmmon.ko
  BTF [M] /tmp/modconfig-FQapFz/vmmon-only/vmmon.ko
Skipping BTF generation for /tmp/modconfig-FQapFz/vmmon-only/vmmon.ko due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/kernels/6.7.7-200.fc39.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-FQapFz/vmmon-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-FQapFz/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory '/tmp/modconfig-FQapFz/vmmon-only'
make: Entering directory '/tmp/modconfig-FQapFz/vmnet-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/6.7.7-200.fc39.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/kernels/6.7.7-200.fc39.x86_64'
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/driver.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/hub.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/userif.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/netif.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/bridge.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/procfs.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/smac_compat.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/smac.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/vnetEvent.o
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/modconfig-FQapFz/vmnet-only/vmnet.o
/tmp/modconfig-FQapFz/vmnet-only/vmnet.o: warning: objtool: VNetCsumAndCopyToUser+0x28: call to csum_partial_copy_nocheck() with UACCESS enabled
/tmp/modconfig-FQapFz/vmnet-only/vmnet.o: warning: objtool: init_module(): not an indirect call target
/tmp/modconfig-FQapFz/vmnet-only/vmnet.o: warning: objtool: cleanup_module(): not an indirect call target
  MODPOST /tmp/modconfig-FQapFz/vmnet-only/Module.symvers
  CC [M]  /tmp/modconfig-FQapFz/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/modconfig-FQapFz/vmnet-only/vmnet.ko
  BTF [M] /tmp/modconfig-FQapFz/vmnet-only/vmnet.ko
Skipping BTF generation for /tmp/modconfig-FQapFz/vmnet-only/vmnet.ko due to unavailability of vmlinux
make[1]: Leaving directory '/usr/src/kernels/6.7.7-200.fc39.x86_64'
/usr/bin/make -C $PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= postbuild
make[1]: Entering directory '/tmp/modconfig-FQapFz/vmnet-only'
make[1]: 'postbuild' is up to date.
make[1]: Leaving directory '/tmp/modconfig-FQapFz/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory '/tmp/modconfig-FQapFz/vmnet-only'
Job for vmware.service failed because a timeout was exceeded.
See "systemctl status vmware.service" and "journalctl -xeu vmware.service" for details.
Unable to start services

If I run systemctl status vmware.service

type or p vmware.service - VMware host virtualization and network services for Workstation
     Loaded: loaded (/usr/lib/systemd/system/vmware.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: timeout) since Mon 2024-03-11 12:16:12 CDT; 17min ago
    Process: 20471 ExecStart=/usr/lib/vmware/scripts/init/vmware start (code=killed, signal=TERM)
        CPU: 86ms

Mar 11 12:15:26 System390 systemd[1]: Starting vmware.service - VMware host virtualization and network services for Workstation...
Mar 11 12:15:26 System390 vmware[20471]: Starting VMware services:
Mar 11 12:15:26 System390 vmware[20471]:    Virtual machine monitor - done
Mar 11 12:15:26 System390 vmware[20471]:    Virtual machine communication interface - done
Mar 11 12:15:27 System390 vmware[20471]:    VM communication interface socket family - done
Mar 11 12:16:12 System390 systemd[1]: vmware.service: start operation timed out. Terminating.
Mar 11 12:16:12 System390 systemd[1]: vmware.service: Failed with result 'timeout'.
Mar 11 12:16:12 System390 vmware[20471]:    Virtual ethernet
Mar 11 12:16:12 System390 systemd[1]: Failed to start vmware.service - VMware host virtualization and network services for Workstation

Here is the output of journalctl -xeu vmware.service

Mar 11 06:20:23 System390 systemd[1]: Failed to start vmware.service - VMware host virtualization and network services for Worksta>
░░ 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 308 and the job result is failed.
Mar 11 12:15:26 System390 systemd[1]: Starting vmware.service - VMware host virtualization and network services for Workstation...
░░ Subject: A start job for unit vmware.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit vmware.service has begun execution.
░░ 
░░ The job identifier is 8704.
Mar 11 12:15:26 System390 vmware[20471]: Starting VMware services:
Mar 11 12:15:26 System390 vmware[20471]:    Virtual machine monitor - done
Mar 11 12:15:26 System390 vmware[20471]:    Virtual machine communication interface - done
Mar 11 12:15:27 System390 vmware[20471]:    VM communication interface socket family - done
Mar 11 12:16:12 System390 systemd[1]: vmware.service: start operation timed out. Terminating.
Mar 11 12:16:12 System390 systemd[1]: vmware.service: Failed with result 'timeout'.
░░ 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 'timeout'.
Mar 11 12:16:12 System390 vmware[20471]:    Virtual ethernet
Mar 11 12:16:12 System390 systemd[1]: Failed to start vmware.service - VMware host virtualization and network services for Worksta>
░░ 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 8704 and the job result is failed.

I do not know what the issue is here.

Thanks!

Jason

barryascott · March 11, 2024, 5:49pm

It always been a strugle to keep VMware working.
But I found that its possible to migrate to QEMU/libvirt.

I migrated from VMware VMs to virt manager successfully.
I have, for example, Windows 11 running as a UEFI BIOS with TPM2.

You have to convert the disk image into qcow2 format and copy the ethernet MAC address from the VMware .XML config file when you setup a new VM in virt manager.

josys36 · March 11, 2024, 6:19pm

I have fought with QEMU enough to know I’ll never touch it again.

vgaetera · March 11, 2024, 6:55pm

Try using an older kernel until the issue is resolved upstream by the VMware developers as is usually the case, although after experiencing similar problems a few more times, you might want to try alternative virtualization solutions once again.

josys36 · March 11, 2024, 7:05pm

It was a problem in Fedora 38 many kernels ago. I don’t see how that’s going to resolve anything especially since it’s working in Kubuntu.

barryascott · March 11, 2024, 10:40pm

I have fought with vmware to know I’ll never touch it again
Until i gave up on it I had been using vmware for 30+ years.
Qemu is working very well for me.

josys36 · March 11, 2024, 10:46pm

Good for you. Doesn’t solve my issue.

computersavvy · March 11, 2024, 11:16pm

I have used QEMU for many years and never seem to have an issue when it is managed with the VMM (virtual machine manager). [Just my $0.02]

josys36 · March 11, 2024, 11:23pm

And again does not help solve my issue.

computersavvy · March 11, 2024, 11:28pm

You seem determined to use a proprietary software on fedora and unwilling to take suggestions to try what has worked for many users for many years and also had many improvements over those years. Good luck.

I suggest you take your problems to the developers of the proprietary software causing problems.

josys36 · March 11, 2024, 11:56pm

You’re so unbelievably helpful.

I didn’t ask anyone what the alternatives are, and just to clarify I HAVE tried and fought with QEMU and I’m not doing that again.

I can run VMWare on Kubuntu just not on Fedora. All I’m looking for is why it’s not working after I get a new desktop. It’s a simple question.

vgaetera · March 12, 2024, 4:53am

As a matter of fact, this forum focuses on opensource virtualization solutions and we can share a lot of experience about libvirt and QEMU/KVM.

We really want to help you, but the most we can do is suggest a workaround since supporting proprietary software is beyond our scope.

Downgrading the kernel is a common workaround for this kind of problem while the proper solution requires to contact the VMware community and their own support channels.

anon91881872 · March 12, 2024, 5:25am

VMware is best to used on LTS kernels since upstream updates for packages and kernels are not 100% this is one reason I moved away from VMware in Linux. Also VMware is slow on updates and fixes so that’s why also is recommended to use LTS

Isn’t Kubuntu based on LTS Ubuntu if so that’s why it is working better

KVM/qemu is really good just you need to know what to do and learning some stuff. Easier and simplest is to use Boxes or Virtual box

But in Fedora you will have lots of issues using VMware

b0r1ng · April 13, 2024, 6:27am

It is impossible:
In 1998, VMware was founded by Diane Greene, Mendel Rosenblum, Scott Devine, Ellen Wang and Edouard Bugnion.

barryascott · April 13, 2024, 6:34am

Apologies only running it 25 years not 30+

b0r1ng · April 13, 2024, 6:51am

@josys36 , I just successfully updated to 6.8.5-201.fc39.x86_64 and had issue with vmnet and vmmon modules (VMware Workstation 17.5.0 build-22583795).
The solution:

Download the missing modules:
wget https://codeload.github.com/mkubecek/vmware-host-modules/tar.gz/refs/heads/workstation-17.5.1
Install them:
tar -zxvf workstation-17.5.1.tar.gz
cd vmware-host-modules-workstation-17.5.1/
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

linuxnoobie · April 23, 2024, 10:27pm

Thank you so much it worked I Just had to tweak the commands abit

wget --debug --inet4-only https://codeload.github.com/mkubecek/vmware-host-modules/tar.gz/refs/heads/workstation-17.5.1

tar -zxvf workstation-17.5.1.tar.gz
cd vmware-host-modules-workstation-17.5.1/
tar -cf vmmon.tar vmmon-only
tar -cf vmnet.tar vmnet-only
sudo cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/
sudo vmware-modconfig --console --install-all

Again thank you sir

Topic		Replies	Views
Vmware buid modules issue Ask Fedora workstation	5	618	June 4, 2024
VMware problems with latest kernel Ask Fedora f34 , vmware , gnome	2	753	October 2, 2021
GNOME Cannot Be Used After Being Updated on Fedora 39 Ask Fedora amd , gnome , virtualbox , f39 , silverblue , workstation	6	384	March 23, 2024
Cannot Compile VMWare Workstation Modul after Upgrade Kernel 5.14.9? Ask Fedora f34 , kernel	23	22843	April 19, 2022
VMWare Kernel module updater Ask Fedora f38 , vmware , workstation	3	1594	October 9, 2023

Problem with VMWare Workstation Pro in Fedora 39

Related topics