| Git Clone URL: | https://aur.archlinux.org/vmware-workstation.git (read-only, click to copy) |
|---|---|
| Package Base: | vmware-workstation |
| Description: | The industry standard for running multiple operating systems as virtual machines on a single Linux PC. |
| Upstream URL: | https://www.vmware.com/products/workstation-for-linux.html |
| Keywords: | dkms ovftool player vmplayer vmware workstation |
| Licenses: | custom |
| Conflicts: | vmware-modules-dkms, vmware-ovftool, vmware-patch, vmware-systemd-services |
| Provides: | vmware-ovftool |
| Submitter: | synthead |
| Maintainer: | jihem |
| Last Packager: | jihem |
| Votes: | 203 |
| Popularity: | 3.30 |
| First Submitted: | 2017-02-10 19:04 (UTC) |
| Last Updated: | 2024-10-11 05:17 (UTC) |
@denji: I found that this is not a good idea. If dracut omits the modules I get systemd warning in the journal:Failed to find module 'vmmon'.
/usr/lib/modules-load.d/vmware.conf is asking systemd to load the modules early at boot. I do not want to mess with this file. May be we need a hook for dkms to rebuild initrd on every dkms run.
@mabod Yes that solves the problem (force rebuild dracut).
Exclude vmnet/vmmon from initramfs.
$ cat /etc/dracut.conf.d/vmware-workstation.conf
omit_drivers+=" vmnet vmmon "
# grub/dracut
$ sudo dracut-rebuild
# systemd-boot/dracut
$ sudo reinstall-kernels
Now it works for me as well. Installing new vmware on top of kernel 6.5.9.arch2-1 did not work at first. I had to recreate all the initrd with dracut. Looks like dracut still loads the old vmware modules from 17.0.2-2 and that crashes the vmware app. Now it is running fine here with all kernels.6.1.60 and 6.5.9
EDIT: I have now added the vmware modules vmnet and vmmon as "omit_drivers" to the dracut conf. I hope that prevents issues like this in the future.
After updating kernel to 6.5.9-arch2-1, PC stopped crashing and vmware workstation 17.5 works again
I'm having the same issue, but I'm on an AMD Ryzen 9 7900X3D. When vmplayer starts, my computer suddenly reboots with no error messages at all. I think one time I switched to a VT and my computer only crashed when I switched back to X, so I assumed it was an amdgpu driver bug. I followed @denji's extremely helpful advice and downgraded and now it's working fine again.
@jihem Checked on 6.1.59 (lts) & 6.5.8 (mainline) kernels, the proposed patch mkubecek/vmware-host-modules@4c2a103 did not change the situation, the problem is with vmware-vmx code (not kernel modules).
@denji If you copy/paste the content of the following link at the end of the file vmmon.patch and rebuild the package, does it solve the problem? (I can't reproduce this problem, so I can't investigate myself)
Pinned Comments
jihem commented on 2020-02-10 17:29 (UTC) (edited on 2021-06-19 13:19 (UTC) by jihem)
After the first installation, please:
1) install the appropriate headers package(s) for your installed kernel(s): linux-headers for default kernel, linux-lts-headers for LTS kernel...
2) reboot or load vmw_vmci and vmmon kernel modules (modprobe -a vmw_vmci vmmon)
3) Enable the services you need (using .service units to activate them during boot or .path units to activate them when a VM is started) :
vmware-networks: to have network access inside VMs
vmware-usbarbitrator: to connect USB devices inside VMs