@normalalkene
I use Wayland, and my kernel models load. Try using ibt=off on the kernel command to see if they compile if using hybrid graphics.
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) |
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 66 Next › Last »
@normalalkene
I use Wayland, and my kernel models load. Try using ibt=off on the kernel command to see if they compile if using hybrid graphics.
@NormalAlkene I don't use Wayland and I don't know how well VMware supports it, but I am sure this is not related to your problem.
I don't know why the command never returns, I never had this kind of problem. If you use a custom kernel, you can try to install the official linux/linux-headers packages instead and see if that fixes it. You can also simply check if the VMware upgrade (version 17.0.0) fixes it.
The command modprobe -a vmw_vmci vmmon
still does not return after hours of wait. And there are no outputs.
Does it have anything to do with Wayland and Sway?
@jihem Thanks. I haven't poked at it, I was hoping the .bundle was like others I've seen (essentially a shell script with a huge binary blob at the end), but that maybe allowed to configure the tmpdir via an env var or an argument.
Both workarounds you describe are better than remounting /tmp , thanks.
The use of the /tmp/vmis.* directory is "hardcoded" inside the .bundle file, when calling mktemp
binary. One workaround is to modify the bundle to use another directory instead, for example with the following command line, before starting makepkg
(of course, the checksum of this file will become wrong):
sed -i -e "s|mktemp -d /tmp/vmis.XXXXXX|mktemp -d ~/AUR/vmware-workstation/tmp/vmis.XXXXXX|" VMware-Workstation-Full-*.x86_64.bundle
Another workaround is to create a new mktemp binary, for example in /usr/local/bin
(to take precedence over /usr/bin/mktemp
), with the following content:
#!/bin/sh
/usr/bin/mktemp -d ~/AUR/vmware-workstation/vmis.XXXXXX
But this binary should be created only during the build of this package.
Unfortunately, I do not see any way to automate this work in the PKGBUILD (except by copying the bundle before patching it, but I prefer avoiding to copy a file of 500MB during the build process).
Thanks for packaging this. Having issues with 16.2.4 when the bundle extracts stuff to /tmp and tries to execute :
~/AUR/vmware-workstation/VMware-Workstation-Full-16.2.4-20089737.x86_64.bundle: line 288: /tmp/vmis.pgU4Bl/install/vmware-installer/vmware-installer: Permission denied
This is of course because /tmp is noexec, as generally recommended.
Any ideas for a workaround, besides remounting /tmp ?
How does one launch this in Wayland instead of XWayland? I use Sway.
@Launch42, you can fix that by adding "ibt=off" to your GRUB command line. The VMWare module doesn't seem to support the new Intel Indirect Branch Tracking (IBT) feature that has been added to Linux 5.18.
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