| 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: | 202 |
| Popularity: | 2.79 |
| First Submitted: | 2017-02-10 19:04 (UTC) |
| Last Updated: | 2024-10-11 05:17 (UTC) |
@class101 That is an interesting idea. I'm not familiar with .socket files and I don't know if it is possible, but it seems to be complicated because it requires that a program started with an unprivileged user starts a root service. We also need to be careful that it may be seen as a security vulnerability.
I'm not motivated enough to search a solution myself, but if someone suggests an elegant solution I could implement it.
@jihem
What would have been awesome, but not sure how is it technically possible, is that instead of asking to enable service files, you could provide .socket files so that the socket will be reponsible of starting the services files when vmware is started, and stopped when vmware is stopped.
It is a good practice under Linux to have the fewest permanent services running, there should be a good reason for a service to run permanently, there is no reason for vmware, and I'm definitely not going to leave them enabled when I don't need them, I will instead start them just before starting up vmware and next boot they won't start automatically.
Like the cups and printers services, logrotate, fstrim, they all use .timer or .socket to work around the need of having services running Permanently, we are on Linux not Windows, Windows is what Windows is today, a big dung that gets slow over time, because of such bad practice :D
16.1.2 builds, installs, and starts on testing... Thanks!
[quote]
GNU nano 5.7 /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/make.log
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/linux/hostif.o] Fehler 1
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/apic.o] Fehler 1
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/comport.o] Fehler 1
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/crosspage.o] Fehler 1
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only/common/cpuid.o] Fehler 1
make[2]: [Makefile:1851: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only] Fehler 2
make[2]: Verzeichnis „/usr/lib/modules/5.12.3-arch1-1/build“ wird verlassen
make[1]: [Makefile:121: vmmon.ko] Fehler 2
make[1]: Verzeichnis „/var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmmon-only“ wird verlassen
make: [Makefile:10: vmmon.ko] Fehler 2
make: Es wird auf noch nicht beendete Prozesse gewartet....
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/driver.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/hub.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/userif.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/netif.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/bridge.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/procfs.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac_compat.o
CC [M] /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac.o
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/driver.o] Fehler 1
make[3]: Es wird auf noch nicht beendete Prozesse gewartet....
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/hub.o] Fehler 1
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/userif.o] Fehler 1
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/netif.o] Fehler 1
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/bridge.o] Fehler 1
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/procfs.o] Fehler 1
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac_compat.o] Fehler 1
cc1: Fehler: incompatible gcc/plugin versions
cc1: Fehler: Plugin ./scripts/gcc-plugins/structleak_plugin.so kann nicht initialisiert werden
make[3]: [scripts/Makefile.build:271: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only/smac.o] Fehler 1
make[2]: [Makefile:1851: /var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only] Fehler 2
make[2]: Verzeichnis „/usr/lib/modules/5.12.3-arch1-1/build“ wird verlassen
make[1]: [Makefile:121: vmnet.ko] Fehler 2
make[1]: Verzeichnis „/var/lib/dkms/vmware-workstation/16.1.2_17966106/build/vmnet-only“ wird verlassen
make: *** [Makefile:10: vmnet.ko] Fehler 2
[/quote]
@malacology it's not possible when using this package. It would be necessary to create another package that only includes the files needed by VMware Player. If the goal is to save disk space, it's probably useless: almost all files are libraries and other data (guest tools, ...) that are needed for both Player and Workstation programs.
How to only leave player and uninstall pro version?
While following this guide: https://wiki.manjaro.org/index.php?title=VMware&mobileaction=toggle_view_mobile
to install on manjaro I ran into an issue where the instillation hung once it reached the line: "Extracting VMware Installer...done."
I looked into the process on htop and found it was simply sitting here doing nothing. Any advice on logs or things I could peek at to see what is going on?
--Edit
It finished building the package but I timed out as a sudoer and had to install i with pacman -U. Still unsure of why it seemed to hang for so long.
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