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: 203
Popularity: 3.30
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 .. 11 12 13 14 15 16 17 18 19 20 21 .. 66 Next › Last »

wiper commented on 2023-02-24 23:02 (UTC) (edited on 2023-02-24 23:03 (UTC) by wiper)

I too am getting the same error:

Error: in prepare, no such column: vmware-tools-linux
  mponent_core_id,longName,description,type) VALUES("vmware-tools-linux","12.1.5
                                      error here ---^

jkotra commented on 2023-02-24 21:27 (UTC)

im getting the following error while trying to install.

Error: in prepare, no such column: vmware-tools-linux
  mponent_core_id,longName,description,type) VALUES("vmware-tools-linux","12.1.5
                                      error here ---^
==> ERROR: A failure occurred in package().
    Aborting...

jihem commented on 2023-02-19 15:03 (UTC) (edited on 2023-02-19 15:05 (UTC) by jihem)

I don't exactly see what is the problem to provide root privileges just the time to enter the license key, but if it is necessary you can apply the following steps:

  • change the owner of the /etc/vmware directory to your unprivileged user
  • enter the license key from command line: /usr/lib/vmware/bin/vmware-vmx --new-sn XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
  • reapply the correct permissions of /etc/vmware directory

I don't know how to do for a trial license, though. It seems VMware GUI ask root permissions even if the current user can write in /etc/vmware.

txtsd commented on 2023-02-19 11:31 (UTC)

Perhaps a link could be created to /opt/vmware/license-ws-* in /etc/vmware/ so the file can be written successfully.

jihem commented on 2023-02-19 07:36 (UTC)

@pfdint The program saves the license (or trial license) in a file on /etc/vmware folder, so it needs root privileges to write this file. But root privileges are only needed to save the license, not for "normal" use (configuring and starting VMs).

pfdint commented on 2023-02-19 06:03 (UTC)

Want to confirm for the record that this program, in order to ultimately operate version 17 and beyond, requires root privileges and a license key, or root privileges even if using a trial. This is true even if a previous version of workstation 16 was working fine.

jihem commented on 2023-01-14 19:37 (UTC)

Hi @yurikoles,

No, I did not forget. Actually, uefitool package is only needed when building this package with the option to include patches for macOS support, and the default build process does not include these patches (because most users don't need them, so I prefer provide them a "vanilla" installation). And I create the .SRCINFO for the default build process, therefore without uefitool.

jihem commented on 2023-01-14 19:21 (UTC)

@gbr It was not an error in the .install file, in the past the directory /etc/vmware-installer was remaining after uninstallation. But you are right, now the remaining directory is /usr/lib/vmware-installer. I will fix that on the next package release. Thanks.

yurikoles commented on 2023-01-13 08:45 (UTC)

Dear @jihem,

You forgot to update .SRCINFO in the latest update.

gbr commented on 2023-01-09 06:39 (UTC)

Minor suggestion for the .install file, which claims there might be leftover files in /etc/vmware-installer:

That path doesn't exist (at least on my machine), but /usr/lib/vmware-installer still does after uninstalling, so I guess you probably meant the latter?

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 66 Next › Last »