Package Details: vmware-workstation 17.6.1-2

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: 204
Popularity: 4.09
First Submitted: 2017-02-10 19:04 (UTC)
Last Updated: 2024-10-11 05:17 (UTC)

Sources (22)

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

Latest Comments

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 66 Next › Last »

jihem commented on 2020-11-11 17:10 (UTC)

My first idea is that your linux and linux-headers packages are not on the same version but I need more informations on your installation to be sure. You use Manjaro, right? What is the result of the command "uname -r"? What are the versions of your packages linux and linux-headers? You can have this information using the commands "pacman -Qi linux" and "pacman -Qi linux-headers". If you use Manjaro, these packages can have a slightly different name, like linux59, linux59-headers, linux58-headers...

mkono87 commented on 2020-11-11 15:30 (UTC)

@jihem modprobe: FATAL: Module vmmon not found in directory /lib/modules/5.9.3-1-MANJARO

Your kernel headers for kernel 5.8.10.arch1-1 cannot be found at /usr/lib/modules/5.8.10.arch1-1/build or /usr/lib/modules/5.8.10.arch1-1/source. You can use the --kernelsourcedir option to tell DKMS where it's located. Im on kernel 5.9 atm and I only see an option for 5.8.14.

jihem commented on 2020-11-09 18:01 (UTC) (edited on 2020-11-09 18:04 (UTC) by jihem)

@haomingbai this message also appears when using the official installation. The proxy.xml file was used on previous VMware versions for shared VMs functionnality. I think it is totally useless now, the fact this message appears is probably a bug.

@mkono87 some verifications to do:

  • do you have linux-headers package installed?
  • if yes, can you check if both linux and linux-headers packages are on the same version, and if this version is 5.8.10.arch1-1?
  • if yes, can you manually load the module vmmon with the command "modprobe vmmon" (launched with root privileges)?
  • if no, do you have the file /usr/lib/modules/5.8.10.arch1-1/kernel/drivers/misc/vmmon.ko on your filesystem?
  • if no, what is the result of the command (with root privileges) "dkms install -m vmware-workstation -v 16.0.0_16894299 -k 5.8.10.arch1-1"?

haomingbai commented on 2020-11-09 10:47 (UTC)

I/O warning : failed to load external entity "/etc/vmware/hostd/proxy.xml" cannot connect to network

mkono87 commented on 2020-11-08 17:51 (UTC)

Iv tried everything but im also getting the modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.8.10-arch1-1

can some help me out. I just cant seem to figure it out after reading the comments on here.

jihem commented on 2020-10-18 12:37 (UTC)

Sffred: it seems something is incoherent in your system, you have two references to the kernel: one in version 5.9.1 (which compiles successfully) and the over in version 5.8.8. Maybe the package linux-headers is in version 5.9.1 and the package linux is still in version 5.8.8, or you boot on a wrong vmlinuz-linux file. But the problem doesn't come from vmware-workstation package.

ericx commented on 2020-10-13 21:50 (UTC)

Solved the "hung at license" problem. It needs to be able to write the license in /etc/vmware/license-ws-160-e4-202001; so run it once as root or make /etc/vmware writable by whomever (at least until the license is written).

ericx commented on 2020-10-13 20:59 (UTC)

After upgrading, workstation 16 opens to request a license key (I provided one), but then the "Finish" button does nothing but dim when clicked and the dialog stays open. kernel modules are loaded, vmware-networks and vmware-usbarbitrator are both running (vmware-authd is not). There are no errors in any log files I can see, permissions are clear for write to ~/.vmware. /etc/vmware/config already says "VMware Player"