@darklyn3r : I have been experiencing the same issues, and I may be wrong, but I chalk them up to the fact that the supported host Linux distributions use way older kernels than Arch does: both linux
and linux-lts
are newer than the newest kernel Ubuntu 22.04 provides, for example. Sure enough, my issues went away when I switched to the 6.1.x LTS kernel branch, which is behind the newest kernel available on some of the supported host distributions. Sadly, the 6.1.x branch is not distributed in binary form by Arch, but it is available on the AUR.
Search Criteria
Package Details: vmware-workstation 17.5.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: | 189 |
Popularity: | 2.56 |
First Submitted: | 2017-02-10 19:04 (UTC) |
Last Updated: | 2024-04-19 18:42 (UTC) |
Dependencies (13)
- dkms
- fuse2
- gcr
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- 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 (linux-headers-binAUR) (optional) – build modules against Arch kernel
Required by (6)
Sources (15)
- config
- configure-initscript.sh
- dkms.conf.in
- https://download3.vmware.com/software/WKST-1751-LX/VMware-Workstation-Full-17.5.1-23298084.x86_64.bundle
- 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
Asuranceturix commented on 2024-05-05 09:59 (UTC)
darklyn3r commented on 2024-05-01 16:07 (UTC)
Since upgrading to version 17 of VMware Workstation, I have experienced several issues. On the one hand, I face unexpected app shutdowns and disconnections from my internet network. Also, I am having difficulty shutting down a virtual machine, as when trying to do so, both the virtual machine and my main Linux operating system freeze and to restore it to a working state, I have to resort to manual shutdown, which is not a solution ideal and could cause additional problems. Is there any solution you can suggest me?
qTO_OTp commented on 2024-04-28 14:27 (UTC)
Hi, I seem to consistently get the same error will upgrading from 17.5.1-1 to 17.5.1-2:
An unknown error occurred during installation. Please check the installation log at /var/log/vmware-installer for more information. ==> ERROR: A failure occurred in prepare(). Aborting... -> error making: vmware-workstation-exit status 4 -> Failed to install the following packages. Manual intervention is required: vmware-workstation - exit status 4
/var/log/vmware-installer contains:
[2023-09-06 23:02:48,049] [2023-09-06 23:02:48,049] [2023-09-06 23:02:48,049] Installer running. [2023-09-06 23:02:48,049] Command Line Arguments: [2023-09-06 23:02:48,049] ['/usr/lib/vmware-installer/3.1.0/vmware-installer.py', '-t', '--console'] [2023-09-06 23:02:48,062] System installer version is: 3.1.0.21581411 [2023-09-06 23:02:48,062] Running installer version is: 3.1.0.21581411 [2023-09-06 23:02:48,062] Opening database file /etc/vmware-installer/database
(It doesn't seem like that log file has changed sins first install)
Anyone else getting a similar error?
jihem commented on 2024-04-19 18:49 (UTC)
@mabod I've added the patch.
mabod commented on 2024-04-15 09:52 (UTC)
There is an (minor) issue that the process vmware-clk is eating up 10 % CPU all the time. This has been discussed in the vmware forum: https://communities.vmware.com/t5/VMware-Workstation-Pro/Workstation-17-5-0-vmware-clk-spinning-on-CPU-when-Linux-VMs-are/m-p/2996282#M183854 A fix is shown in that forum. It works fine for me. And the patch is very small.
@jihem: You may want to add this patch to the PKGBUILD. I have done this for myself and can share with you if you want.
iTzGooDLife commented on 2024-04-08 15:22 (UTC)
I updated yesterday and since the update I've been experiencing many issues with connections to remote VMs. The windows are getting cut off and the transition between them is slow. My vmware version is 17.5.1-1, kernel 6.8.4.arch1-1 and video card nvidia. Does anyone have the same issue?
jihem commented on 2024-04-06 09:50 (UTC)
Sorry, this is fixed.
alexeybes93 commented on 2024-04-05 21:54 (UTC) (edited on 2024-04-05 21:54 (UTC) by alexeybes93)
checksum failed for vmmon.patch and vmnet.patch
56519232870055e6cacd62bc830127cbbdc30554c4ffffa381c8c108b50f739f vmmon.patch
4332a189c79ce15fa4d59dc45cffc78f42f48cfbb059b5eeafbb43a9cac835ba vmnet.patch
jihem commented on 2024-04-05 16:42 (UTC)
@sand7000 actually, I don't have to add debugedit
as dependency, because it is included in the group base-devel
which is required to install before building any package from AUR.
However, it is asked to install debugedit
because vmware-workstation
is built with the option debug
, which is irrelevant for packages that don't compile anything. So, I have updated the PKGBUILD to remove the debug
option.
sand7000 commented on 2024-04-05 14:58 (UTC)
Seems to be missing a required build dependency. I see the error:
==> ERROR: Cannot find the debugedit binary required for including source files in debug packages.
Installing:
https://archlinux.org/packages/core/x86_64/debugedit/
resolved the issue.
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