| 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: | 204 |
| Popularity: | 4.09 |
| First Submitted: | 2017-02-10 19:04 (UTC) |
| Last Updated: | 2024-10-11 05:17 (UTC) |
@ihipop Yes, I have read the instruction. If you go to check the vmware-networks.service, you will find that the service wants vmware-networks-configuration.service, which will run the configuration service first.
And I also tried stopping the services, deleting the configuration files generated before, and followed the instructions. But that was still not working for me.
@BryanLiang read the instruction carefully, it has been mentioned: vmware-networks-configuration.service
@ihipop Thanks for your advice. My situation is that I loaded the kernel modules first and start the vmware-networks.service directly. Now the network is working for my virtual machines, but I cannot open the network editor.
I am not able to open Virtual Network Editor. Has any one else had this problem?
I'm having trouble installing this package. Running makepg ends with: ==> Starting prepare()... Extracting VMware Installer...done. ==> ERROR: A failure occurred in prepare(). Aborting...
I can't even extract the bundle manually: % sh src/VMware-Workstation-17.5.2-23775571.x86_64.bundle --extract /tmp Extracting VMware Installer...done. % echo $? 1 It results in exit code 1 and /tmp stays untouched.
Is it possible to have this installed along side vmware-vmrc? I get similar conflicts to rado84, but it tells me the files are already owned by vmware-vmrc
when the bundle tries to install
The bundle should never try to install anything. You shouldn't manually start the bundle if you want to install VMware from this AUR package, and the PKGBUILD only extracts the files from the bundle to install them using its own script (it doesn't start the bundle installation).
Unfortunately, IDK how to force the aur helper (trizen) to write on the root partition. AFAIK trizen can not be run as sudo.
After re-reading your first comment, I think you don't understand how AUR works. To install this package, you should only start the command trizen -S vmware-workstation (or something similar, I don't know trizen syntax). Then trizen downloads the PKGBUILD in a directory, starts makepkg in this direcory and when the package is built, trizen uses pacman to install the package. Only pacman needs root privileges and is able to write files anywhere on the filesystem (I guess trizen uses sudo pacman -U, makepkg -i or something like that to run pacman with root privileges).
If you are sure to use trizen correctly, then maybe this is a trizen bug, so try with the manual method: https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages
rado84, Are you using any other AUR packages that maybe in conflict, because your issue doesn't happen with my systems.
@jihem, yes and I deleted them manually one by one, thus cleaning the system from everything vmware related. And then at the end of the installation the story repeats itself. So I backed up the current system, installed a fresh Arch with nothing else but the desktop and video driver and tried installing VMWare again - same thing: at the end of the installation "these files exist in the filesystem". Clearly one of the other files in the above list provides these files prematurely and when the bundle tries to install, it can't because of these conflicts. It's pointless, I'll use vbox. VMWare has become (to me) the same thing Skype did ever since MS bought it - something not to touch, if I wanna keep my sanity intact.
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