Package Details: vmware-workstation 17.6.2-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: JulianXhokaxhiu
Last Packager: jihem
Votes: 207
Popularity: 3.54
First Submitted: 2017-02-10 19:04 (UTC)
Last Updated: 2024-12-20 10:44 (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 .. 29 30 31 32 33 34 35 36 37 38 39 .. 67 Next › Last »

jihem commented on 2020-07-25 05:57 (UTC)

@dvb I think the more simple way is to open vmware with root (sudo vmware) and ask a trial license.

dvb commented on 2020-07-24 23:17 (UTC)

Anyone knows how I am supposed to workaround that "entering the serial as root" by doing sudo /usr/lib/vmware/bin/vmware-enter-serial for getting rid of as non-root user ==== AUTHENTICATING FOR org.freedesktop.policykit.exec ==== Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user if I don't have any serial because I just want to use VMWare Player which is free to use?

Jeffprod commented on 2020-06-29 09:31 (UTC)

@aizomul I had the same issue :

==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user

This was because i was entering a licence number, and for any reason this must be done as root. So the solution is to make it once :

sudo /usr/lib/vmware/bin/vmware-enter-serial

Then you can start vmware as normal user.

fosskers commented on 2020-06-11 17:28 (UTC)

To Aura users trying to install this package and having issues: upgrade Aura to 3.1.3 (or later) and the issue will be solved.

Apologies to @jihem for the spam this caused him.

jihem commented on 2020-05-30 10:33 (UTC)

CaskAle13c: I already started to create a package for this version, but I didn't spend time to test it. You could be able to build the package by applying the following patch on the current PKGBUILD version: https://pastebin.com/Uri4Y2ej

CaskAle13c commented on 2020-05-28 21:19 (UTC)

@jihem, Have you, by any chance, tried out your package build on the Workstation Pro 20H2 Tech Preview?

https://communities.vmware.com/community/vmtn/beta/workstation-pro

jihem commented on 2020-05-09 10:02 (UTC)

sizzen: After the first installation of this package, you should never have to manually load the vmmon module because it is already loaded at startup (see /usr/lib/modules-load.d/vmware.conf). So, after a kernel update and before reboot, the module compiled for the running kernel is already loaded (no need to load it again) and during the reboot the module compiled for the new kernel version is loaded (no need to load it too).

sizzen commented on 2020-05-08 07:15 (UTC)

5.6.11-arch1-1 modprobe: WARNING: Module vmmon not found in directory /lib/modules/5.6.11-arch1-1

When I load the kernel modules after a system update vmnom does exist. Do I need to install the new package everytime there is a kernel update or is there another way around this?

xanadu73 commented on 2020-05-03 13:15 (UTC)

jihem: I'll look into that, thank you.

jihem commented on 2020-05-03 10:18 (UTC)

xanadu73: I never add this problem, on this package or any other using DKMS. I think something is broken in your installation. Do you use a package (like kernel-modules-hook) that change the behaviour of DKMS or kernel modules management? It could be the reason. Or maybe some previous modules was not uninstalled correctly. Check with dkms status if you only have the modules related to your current kernels installed.