In version 16.1.0-1 my problem was solved with the USB controller.
Search Criteria
Package Details: vmware-workstation 17.6.1-2
Package Actions
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) |
Dependencies (13)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- fuse2
- gcr
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- gtkmm3
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libaio (libaio-gitAUR)
- libcanberra
- libxcrypt-compat
- pcsclite (pcsclite-gitAUR)
- vmware-keymapsAUR
- sqlite (sqlite-fossilAUR) (make)
- linux-headers (optional) – build modules against Arch kernel
Required by (6)
Sources (22)
- config
- configure-initscript.sh
- dkms.conf.in
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linux-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-linuxPreGlibc25-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-netware-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-solaris-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPre2k-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.5.2/23775571/linux/packages/vmware-tools-winPreVista-12.4.0-23259341.x86_64.component.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/core/VMware-Workstation-17.6.1-24319023.x86_64.bundle.tar
- https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.1/24319023/linux/packages/vmware-tools-windows-12.4.5-23787635.x86_64.component.tar
- Makefile
- vmmon.patch
- vmnet.patch
- vmware-bootstrap
- vmware-environment.sh
- vmware-networks-configuration.service
- vmware-networks.path
- vmware-networks.service
- vmware-usbarbitrator.path
- vmware-usbarbitrator.service
- vmware-vix-bootstrap
Latest Comments
« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 66 Next › Last »
injured commented on 2020-11-23 16:34 (UTC)
sizzen commented on 2020-11-21 19:59 (UTC)
Has anyone had luck with using vmware workstation with KDE plasma with wayland instead of X? You cannot run gui applications as root under wayland which I understand the security behind but then how do I run it if it requires root ? Any help would be appreciated.
injured commented on 2020-11-21 10:01 (UTC) (edited on 2020-11-21 10:45 (UTC) by injured)
When I create a new virtual machine under macOS, I have USB Controller set to USB Compatibility: 3.1. By launching the installation, the USB 3.1 option disappears and only 1.1 and 2.0 remain. I get the message: "Using USB devices with a USB 3.1 controller may require additional drivers to be installed in the guest." I know running macOS on vmware requires USB 3.1. Anyone have an idea why USB 3.1 is disappearing from my list?
brandimarte commented on 2020-11-19 13:33 (UTC)
I found a solution that worked for me here. The idea is to install polkit-gnome
, then run:
$ /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &
$ vmplayer
This will prompt a window for the sudo password and after that wmplayer runs normally. Apparently it's only needed in the first run. I've removed the installation of polkit-gnome
and I can still run vmware without root privileges.
brandimarte commented on 2020-11-19 11:08 (UTC)
I'm trying to use wmplayer, but then it prompts a welcome window where I choose "Use WMware Player 16 for free for non-commercial use" and when I click "Finish" the following error appears in the terminal:
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/lib/vmware/bin/vmware-setup-helper' as the super user
Authenticating as: xxxx@yyyy,,,, (xxxx)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized
This incident has been reported.
where xxxx is my login name and yyyy is the hostname. I can only execute wmplayer as sudo. Anyone here had a similar issue and could recommend a solution? Thanks!
obelix1502 commented on 2020-11-18 22:30 (UTC)
Anyway, kernel 58 is out of date, so for vmware and vmmon 58 it doesn't matter anymore. I didn't make any modification and it works perfectly under the LTS 59 kernel.
injured commented on 2020-11-18 18:14 (UTC)
Installing macOS 11.0.1. Kernel 58, then 59. Loop during installation on both kernels. Anyone had such a condition?
jihem commented on 2020-11-11 18:34 (UTC)
Ok. Clearly I don't understand how Manjaro handles kernels, but in the future you should always check that you use the same version of linuxXX and linuxXX-headers to avoid this problem. Also, I don't know why you had a reference to 5.8.10 version on your first message, maybe you installed linux58-headers, in that case you can probably remove it now.
mkono87 commented on 2020-11-11 17:38 (UTC) (edited on 2020-11-11 17:53 (UTC) by mkono87)
@jihem uname - r results in 5.9.3-1-MANJARO
I then installed the linux59-headers
pacman -Qi linux-headers results in
Name : linux54-headers
Version : 5.4.74-1
Description : Header files and scripts for building modules for Linux54 kernel
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2
Groups : None
Provides : linux-headers=5.4.74
Depends On : None
Optional Deps : None
Required By : linux-lts-headers
Optional For : dkms vmware-workstation
Conflicts With : None
Replaces : None
Installed Size : 46.92 MiB
Packager : Manjaro Build Server <build@manjaro.org>
Build Date : Sun 01 Nov 2020 08:42:10 AM
Install Date : Wed 11 Nov 2020 10:18:02 AM
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
Yes im running Manjaro. In kernels its says im running 5.9
EDIT: by running modprobe vmmon again it seems to be working. Well except for networking but im working on that.
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...
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