Are the Linux guest tools from VMware even necessary anymore? I've been using open-vm-tools for years (as recommended by VMware themselves).
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: | 202 |
Popularity: | 2.32 |
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 2 3 4 5 6 7 8 9 .. 66 Next › Last »
ajgringo619 commented on 2024-09-05 21:24 (UTC)
jihem commented on 2024-09-05 20:21 (UTC)
If someone know where the latest guest tools can be publicly downloaded, it would help me a lot to update the package to 17.6. Only Windows guest tools are available on this link: https://softwareupdate.vmware.com/cds/vmw-desktop/ws/17.6.0/24238078/linux/packages/
Emonora commented on 2024-08-17 15:07 (UTC)
Yes, I do have the linux headers on the latest version. Running dkms install vmware-workstation/17.5.2_23775571 -k 6.10.5-arch1-1
seems to fix the issue. The vmware-networks.service starts fine now. Thanks for your help!
jihem commented on 2024-08-17 04:15 (UTC)
@Emonora Do you have linux-headers
installed? Is it to the same version than linux
(6.10.5-arch1-1)? If not, fix that.
Otherwise, what is the result of the command dkms status
? What happens if you force the recompilation and reinstallation of kernel modules with dkms install vmware-workstation/17.5.2_23775571 -k 6.10.5-arch1-1
?
Emonora commented on 2024-08-16 22:06 (UTC) (edited on 2024-08-16 22:06 (UTC) by Emonora)
Hai. I've been using this package for vmware as of recently, and upon updating to the latest version of the OS (9.10.5-arch1-1) The module vmware-networks.service will not start, and outputs the following error when you look through it's logs.
Aug 16 16:41:21 arch modprobe[33542]: modprobe: FATAL: Module vmnet not found in directory /usr/lib/modules/6.10.4-arch2-1
It seems to be looking for the module in the old directory, however, the directory (6.10.4-arch2-1), is completely empty aside from one file. The file in question is the modules.weakdep
file which only contains one line, that being the following:
# Weak dependencies extracted from modules themselves.
I have tried and failed numerous times to resolve the issue, and I was wondering if anyone had a solution that worked or knew if the repo needed an update.
cezar commented on 2024-07-25 18:53 (UTC)
@jihem I have vanilla Arch, but with multilib enabled... I disabled multilib (pacman.conf) and removed all the 32bit libraries and clean reinstalled vmware and now it's working. Thank you for pointing me in the right direction!
jihem commented on 2024-07-25 16:07 (UTC)
It seems an incompatibility between dependencies. Do you use vanilla Arch or a distro based on it? The symbol __strlen_avx2
intrigues me, it seems you have installed packages optimized for your processor architecture.
Anyway, you can uncomment the line export VMWARE_USE_SHIPPED_LIBS=yes
in file /etc/conf.d/vmware
to force VMware to use its built-in dependencies, maybe it will fix this issue.
cezar commented on 2024-07-24 21:16 (UTC) (edited on 2024-07-25 08:09 (UTC) by cezar)
Hello,
I recently installed this package:
$ pacman -Qi vmware-workstation
Name : vmware-workstation
Version : 17.5.2-3
$ pacman -Qi linux
Name : linux
Version : 6.10.arch1-2
$ pacman -Qi glibc
Name : glibc
Version : 2.40-1
$ lsmod | egrep "vmw_vmci|vmmon"
vmmon 163840 0
vmw_vmci 118784 0
and for some reason all the vmware's binaries causes a segmentation fault:
[ 1441.287765] vmware[8273]: segfault at 0 ip 00007318b94de2dd sp 00007ffe1ed4b328 error 4 in libc.so.6[16f2dd,7318b9393000+171000] likely on CPU 3 (core 3, socket 0)
[ 1441.287773] Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66
$ gdb -core=/var/lib/systemd/coredump/core.vmware.1000.2f22cadb1328419bb5b5b0f83c27cc47.7416.1721854782000000 /usr/lib/vmware/bin/vmware
GNU gdb (GDB) 15.1
...
Reading symbols from /usr/lib/vmware/bin/vmware...
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
(No debugging symbols found in /usr/lib/vmware/bin/vmware)
[New LWP 7416]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/vmware/bin/vmware'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
76 VPCMPEQ (%rdi), %ymm0, %ymm1
(gdb) bt
#0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
#1 0x000063a96e8f38b2 in ?? ()
#2 0x000063a96e8f6057 in ?? ()
#3 0x000063a96e8f26ef in ?? ()
#4 0x000073642949fe08 in __libc_start_call_main (main=main@entry=0x63a96e8f21e0,
argc=argc@entry=1, argv=argv@entry=0x7fffdf925d78)
at ../sysdeps/nptl/libc_start_call_main.h:58
#5 0x000073642949fecc in __libc_start_main_impl (main=0x63a96e8f21e0, argc=1,
argv=0x7fffdf925d78, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffdf925d68) at ../csu/libc-start.c:360
#6 0x000063a96e8f3045 in ?? ()
#7 0x00007fffdf925d68 in ?? ()
#8 0x0000000000000038 in ?? ()
#9 0x0000000000000001 in ?? ()
#10 0x00007fffdf9263a1 in ?? ()
#11 0x0000000000000000 in ?? ()
Any suggestions?
Thank you, Cezar
jihem commented on 2024-07-19 22:20 (UTC)
Ok, I've reverted the last commit since it causes more problems for some people.
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