| 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: | 192 |
| Popularity: | 4.74 |
| First Submitted: | 2017-02-10 19:04 (UTC) |
| Last Updated: | 2024-05-16 21:20 (UTC) |
I just noticed, as soon as I enable networking
$ sudo systemctl start vmware-networks.service
my journal gets spammed with these messages, non stop and as far as I can tell it never ends spamming.
Apr 07 13:31:57 main kernel: userif-10: sent link up event.
Apr 07 13:31:58 main vmnet-natd[1736]: RTM_NEWADDR: index:2, addr:192.168.0.15
Couldn't find anything searching for it. Does anyone experience something similar or can give me a pointer how to fix it?
Thanks
@jihem
I accepted uefitool and in latest update made binary artifacts names lower-case in accordance to other uefitool-* packages. So please update line 412 of this PKGBUILD accordingly.
/var/lib/dkms/vmware-workstation/16.2.3_19376536/build/vmnet-only/bridge.c:956:36: error: passing 'const unsigned char *' to parameter of type 'uint8 *' (aka 'unsigned char *') discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
SMAC_SetMac(bridge->smac, bridge->dev->dev_addr);
^~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/vmware-workstation/16.2.3_19376536/build/vmnet-only/./smac.h:75:45: note: passing argument to parameter 'mac' here
SMAC_SetMac(struct SMACState *state, uint8 *mac); // IN: state, and host MAC
^
1 error generated.
Anyone knows how to fix this error on DKMS compilation?
@LevitatingRein This is normal, because contrary to the official VMware installer, this package does not place any file in /etc/init.d. Daemons are installed as systemd units. And there is no equivalent systemd service for /etc/init.d/vmware; see https://wiki.archlinux.org/title/VMware#Package_build_for_x86_64 to know which services can be enabled.
I just did a system upgrade and /etc/init.d disappeared.
I reinstalled this package but the /etc/init.d/vmware file is not coming back.
Hello,
On the last 16.2.1-4 version, if you enable "_enable_macOS_guests=y" in PKGBUILD, you have the following error :
-> Téléchargement de unlocker-3.0.7.py…
...
curl: (22) The requested URL returned error: 404
==> ERREUR : Erreur lors du téléchargement de https://raw.githubusercontent.com/DrDonk/unlocker/v3.0.7/unlocker.py
Unlocker has now new versions (not python anymore, it seems ?), and 3.0.7 does not seem to be there anymore.
Thank you.
Best regards,
ZEBofx
I'm using Manjaro Upgraded using Pamac GUI. It noted the Libcrypt-compat dependency and installed it. Everything works fine.
For people using Manjaro, the best solution is probably to not update this package for the moment (stay on 16.2.1-3). libxcrypt-compat dependency is useless for you, it seems that your glibc package already contains the required library. Just be careful during the next system upgrades: when glibc package will be updated, you will probably be able to update this package.
Greetings!
My system is Manjaro KDE.
Same issue:
Could not find all required packages:
libxcrypt-compat (Wanted by: vmware-workstation)
I've downloaded libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst
I've tried: sudo pacman -U --asdeps libxcrypt-compat-4.4.28-2-x86_64.pkg.tar.zst
The system's answer is:
error: failed to commit transaction (conflicting files)
libxcrypt-compat: /usr/lib/libcrypt.so.1 exists in filesystem (owned by glibc)
Errors occurred, no packages were upgraded.
No idea what to do next.
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