| 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: | JulianXhokaxhiu |
| Last Packager: | JulianXhokaxhiu |
| Votes: | 212 |
| Popularity: | 3.33 |
| First Submitted: | 2017-02-10 19:04 (UTC) |
| Last Updated: | 2025-04-03 21:57 (UTC) |
Does not build when using a 6.12 kernel:
Error! Bad return status for module build on kernel: 6.12.5 (x86_64)
Consult /var/lib/dkms/vmnet/1/build/make.log for more information.Error! Bad return status for module build on kernel: 6.12.5 (x86_64)
Consult /var/lib/dkms/vmware-workstation/17.6.1_24319023/build/make.log for more information.The error logs are quite long.
@ThePirate42 The fact the modules are in-tree or built by DKMS is not important. vmmon and vmw_vmci are necessary to launch a VM, but they are not automatically loaded by the kernel. After reboot, they are loaded thanks to the file /usr/lib/modules-load.d/vmware.conf, but just after the installation you need to load them manually if you don't want to reboot.
vmnet is loaded when the service vmware-networks.service is started, so it is not necessary to load it manually. You just have to start/enable the service if you need the network functionnality.
Maybe I'm misunderstanding something, but shouldn't the pinned comment ask to reload vmnet instead of vmw_vmci? Since vmnet is being installed with DKMS, while vmw_vmci is already included upstream.
omano commented on 2024-10-11 00:21 (CEST)
You forgot to update the checksum of vmware-tools-windows
To be clear, it builds OK once you update the checksum manually in the PKGBUILD on my side. Just that you have to manually edit the PKGBUILD because when the new version of the tool was added, the old checksum stayed. //EDIT: the PKGBUILD has been updated anyway.
@ josemanuelp: do a Clean Build. See if you still have issues.
error: command failed: /home/josemanuelp/.cache/paru/clone/vmware-workstation: git diff --stat --patch --cached --color=always -- :!.SRCINFO:
thread 'main' panicked at /build/.cargo/registry/src/index.crates.io-6f17d22bba15001f/line-numbers-0.3.0/src/lib.rs:105:13:
Offset 646 is out of bounds for a string of length 645
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal: external diff died, stopping at vmmon.patch
==> Validating source files with sha256sums...
VMware-Workstation-17.6.1-24319023.x86_64.bundle.tar ... Passed
vmware-tools-linux-12.4.0-23259341.x86_64.component.tar ... Passed
vmware-tools-linuxPreGlibc25-12.4.0-23259341.x86_64.component.tar ... Passed
vmware-tools-netware-12.4.0-23259341.x86_64.component.tar ... Passed
vmware-tools-solaris-12.4.0-23259341.x86_64.component.tar ... Passed
vmware-tools-windows-12.4.5-23787635.x86_64.component.tar ... FAILED
vmware-tools-winPre2k-12.4.0-23259341.x86_64.component.tar ... Passed
vmware-tools-winPreVista-12.4.0-23259341.x86_64.component.tar ... Passed
vmware-bootstrap ... Passed
vmware-vix-bootstrap ... Passed
config ... Passed
configure-initscript.sh ... Passed
vmware-environment.sh ... Passed
vmware-networks-configuration.service ... Passed
vmware-networks.service ... Passed
vmware-usbarbitrator.service ... Passed
vmware-networks.path ... Passed
vmware-usbarbitrator.path ... Passed
dkms.conf.in ... Passed
Makefile ... Passed
vmmon.patch ... Passed
vmnet.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
You forgot to update the checksum of vmware-tools-windows
Sure seems like it...
You forgot to update the checksum of vmware-tools-windows
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