_enable_macOS_guests=y doesn't work any more :( The repository is deleted.
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 .. 32 33 34 35 36 37 38 39 40 41 42 .. 66 Next › Last »
friday commented on 2019-12-21 04:36 (UTC)
jrbaldridge commented on 2019-12-19 22:28 (UTC)
It looks like vmware-networks-configuration.service is currently triggered by any of the following files missing:
/etc/vmware/networking /etc/vmware/vmnet1/dhcpd/dhcpd.conf /etc/vmware/vmnet1/dhcpd/dhcpd.leases /etc/vmware/vmnet8/dhcpd/dhcpd.conf /etc/vmware/vmnet8/dhcpd/dhcpd.leases /etc/vmware/vmnet8/nat/nat.conf
Unfortunately this means if you remove vmnet1 or vmnet8, vmware-networks-configuration.service will be triggered and reconfigure all your networks. It looks like /etc/vmware/networking alone should provide a sufficient trigger, as it only exists post-network configuration, and will exist for any defined network configuration.
Here's a patch to only trigger vmware-networks-configuration.service if /etc/vmware/networking does not exist.
From f922f5a5051b87adcfed39588138b11903fdc98f Mon Sep 17 00:00:00 2001
From: Jared Baldridge <jrbaldridge@lbl.gov>
Date: Thu, 19 Dec 2019 14:09:27 -0800
Subject: [PATCH] adjust vmware-networks-configuraiton.service conditions
---
vmware-networks-configuration.service | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/vmware-networks-configuration.service b/vmware-networks-configuration.service
index 779b01a..0d86867 100644
--- a/vmware-networks-configuration.service
+++ b/vmware-networks-configuration.service
@@ -1,11 +1,6 @@
[Unit]
Description=VMware Networks Configuration Generation
-ConditionPathExists=|!/etc/vmware/networking
-ConditionPathExists=|!/etc/vmware/vmnet1/dhcpd/dhcpd.conf
-ConditionPathExists=|!/etc/vmware/vmnet1/dhcpd/dhcpd.leases
-ConditionPathExists=|!/etc/vmware/vmnet8/dhcpd/dhcpd.conf
-ConditionPathExists=|!/etc/vmware/vmnet8/dhcpd/dhcpd.leases
-ConditionPathExists=|!/etc/vmware/vmnet8/nat/nat.conf
+ConditionPathExists=!/etc/vmware/networking
[Service]
UMask=0077
--
2.24.1
tech101usa commented on 2019-12-11 06:33 (UTC)
Thank you so much for your efforts to maintain this package. Having VMware Workstation on Arch and its derivatives via the AUR is so extremely helpful.
I'm actually on Manjaro and recently ran a system-wide upgrade that included a Kernel update from 5.3 to 5.4. As expected, this broke my Workstation 15 install. However, removing and reinstalling following the direction provided solved the issue with one exception. When I reinstalled, I didn't realize I still had only the Linux53 headers installed and not the Linux54 headers. The vmmon module wasn't built during the install as a result.
Uninstalling Workstation 15, removing the Linux53 headers (I'm not expecting to revert to the 5.3 kernel anytime soon), installing the Linux54 headers, and then reinstalling Workstation 15 from the AUR solved the issues.
Very grateful for your work in making this available.
THANK YOU!!!
jihem commented on 2019-11-16 20:38 (UTC)
@redsolja: I've fixed the PKGBUILD.
@majed17: I don't have this kind of problem. Maybe this is a bug with the Cinnamon screen locker. You should try with another desktop environment or another screen locker before trying another distribution.
redsolja commented on 2019-11-15 21:28 (UTC)
Hello, after the latest update to VMware-Workstation-Full-15.5.1-15018445.x86_64.bundle, vmware was silently failing.
Logs under /tmp showed that there was a GLIB error complaining about two EULA files:
2019-11-16T23:13:10.971+02:00| vmui| W115: Unhandled Glib exception: class 'N4Glib9FileErrorE', details 'Failed to open file “/usr/share/doc/vmware-workstation/EULA”: No such file or directory'
and
2019-11-16T23:21:31.815+02:00| vmui| W115: Unhandled Glib exception: class 'N4Glib9FileErrorE', details 'Failed to open file “/usr/lib/vmware-ovftool/vmware.eula”: No such file or directory'
I fixed this with:
cd /usr/share/doc/
mkdir vmware-workstation
cd vwmare-workstation
cp /home/USERNAME/aur/vmware-workstation/pkg/vmware-workstation/usr/share/licenses/vmware-workstation/VMware\ Workstation\ -\ EULA.txt EULA
cd /usr/lib/vmware-ovftool/
cp /usr/share/licenses/vmware-workstation/VMware\ OVF\ Tool\ -\ EULA.txt vmware.eula
majed17 commented on 2019-11-15 11:02 (UTC)
does anybody have win 10 virtual machines on the new workstation version? on linux mint it keeps crashing when i lock the screen! does that happen on arch?
jihem commented on 2019-11-14 21:50 (UTC)
Thanks for your feedback! Yes, this solution exists but is not perfect because I'm afraid that Player refuses to start after 30 days. I'm interested if someone could tell me what happen after this delay.
However, even if Player refuses to start, it's probably possible to ask a new trial after removing the file /etc/vmware/license-ws-150-e1-201804
josete commented on 2019-11-14 19:43 (UTC) (edited on 2019-11-14 19:44 (UTC) by josete)
I can confirm the solution. You only have to run vmware just one time, instead of vmplayer. After that, you won't see again the prompt.
<deleted-account> commented on 2019-11-14 19:38 (UTC)
@jihem I "solved" this problem by launching VMware Workstation (the paid version) and selecting a 30-day trial. This made the license prompt disappear from VMware Player and everything works as before.
I haven't done this more than 30 days ago, though, so perhaps once the trial is over the prompts will reappear. I hope not!..
Edit: It seems this has already been talked about down below. However, I don't see any license countdown in Player.
jihem commented on 2019-11-14 19:25 (UTC)
I've updated the package. Unfortunately the problem with VMware Player license is still present. It seems this update mostly includes security fixes.
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