Package Details: vmware-workstation 25H2-4

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: JulianXhokaxhiu
Last Packager: JulianXhokaxhiu
Votes: 236
Popularity: 3.78
First Submitted: 2017-02-10 19:04 (UTC)
Last Updated: 2025-10-21 20:09 (UTC)

Sources (27)

Pinned Comments

JulianXhokaxhiu commented on 2025-10-21 20:11 (UTC)

New package version released: 25H2-4

Changelog:

  • Thanks for the feedback as usual. This version fixes the DKMS old/new kernel detection. While i was doing bit of cleanup to onboard the new 25H2 version by mistake I lost one patch which was vital for allowing new kernels to be build on top of new headers. Issue was that the default Makefiles from vmware always considered the running kernel the one used to build modules, while if you're in the middle of an upgrade you want to build it for the new version ( a custom flow however introduced by pacman and libalpm ). Anyway, long story short this behavior is back again and starting this version you should be able to upgrade without trouble ( and probably this fixes as well the other reports I've seen around CachyOS ).

Enjoy!

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

Latest Comments

1 2 3 4 5 6 .. 89 Next › Last »

jimedrand commented on 2026-02-09 01:44 (UTC)

As the libx11 package (mr293) has been removed from AUR in anticipation of an update to version 1.8.13, there is no need to worry about VMware closing unexpectedly in a Wayland session in future. Simply wait for the next libx11 update to version 1.8.13 in the extra repository, then upgrade libx11 once it is available.

gabrielkorytiak commented on 2026-02-05 04:59 (UTC)

works fine so far still need to use "setxkbmap us" as workaround

MBILC commented on 2026-01-14 18:28 (UTC) (edited on 2026-01-14 18:49 (UTC) by MBILC)

Hello,

[EDIT] Just came across this, might be the same issue https://www.reddit.com/r/vmware/comments/1iqu7wp/workstation_wayland_on_the_host_broken_special/
[2ND EDIT] Testing out setting a Window rule to ignore global keys https://community.broadcom.com/vmware-cloud-foundation/question/wayland-support

Firstly, thank you JulianXhokaxhiu for these fixes! As i use Windows VMs, QEMU/KVM just lacks the performance under windows so workstation it is for now.

I have used your fixed (libx11-mr293) and things are working great, for the most part.

Wanted to see if this is a known issue and if it is related to this patching specifically, or a 25H2 bug in general. Previously, I was on Mint 22 running 6.14 kernel and running 25H2 and did not experience this issue.

*OS Info:

OS: CachyOS x86_64
Kernel: Linux 6.18.5-2-cachyos
Packages: 1502 (pacman)
Shell: fish 4.3.3
DE: KDE Plasma 6.5.4
WM: KWin (Wayland)

When I have vmware workstation open, in full screen, even if I am not active with in the Windows 11 VM I have running, the VM is capturing keyboard commands from my host OS.

Example, If I have notepad open in the VM, and I go out to my host and go into a browser window and do a select all, the Windows VM registers my ctrl+A command and prints out a bunch of aaaaaaaaa into notepad, or any other active input field in the VM. So far seems related to ctrl+* commands, seperate from the ones VMware uses (https://techdocs.broadcom.com/us/en/vmware-cis/desktop-hypervisors/workstation-pro/25H2/using-vmware-workstation-pro/installing-and-using-workstation-pro/using-the-workstation-pro-window/default-hot-key-combinations.html)

*My VMware workstation preferences are set to

Checked: "Grab keyboard and mouse input on mouse click"
Unchecked: "Grab keyboard and mouse input on key press"
Checked: Automatically grab and ungrab the mouse cursor

manywolves commented on 2026-01-14 10:52 (UTC)

@javierpeces, you are experiencing the upstream libx11 issue mentioned in the comments immediately before yours, please make sure to read them next time.

For now you can install the AUR package https://aur.archlinux.org/packages/libx11-mr293 to workaround the issue until the upstream merge request, https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/293 is implemented.

jimedrand commented on 2026-01-14 01:30 (UTC)

To anybody that have facing these issues below:

$ GDK_SYNCHRONIZE=1 vmware Cannot load message dictionary "/usr/lib/vmware/messages/es/vmware-mks.vmsg".

(vmware-tray:18948): Gdk-WARNING **: 03:47:29.104: The program 'vmware-tray' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 521 error_code 2 request_code 135 (XKEYBOARD) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

These program only runs better on X11. That means you can't run properly on newer GNOME or any DE/WM with Wayland as the default (especially if they only offer Wayland). Because VMware Workstation is still heavily using the older GTK3 frame, which might not be compatible with Wayland. There's no more solution rather than using another DE/WM that still supports X11.

javierpeces commented on 2025-12-30 02:51 (UTC)

Installed the new 25H2 package. UI crashes. It works properly in Ubuntu LTS. Looks like it does not like the Wayland version present in Arch.

$ GDK_SYNCHRONIZE=1 vmware Cannot load message dictionary "/usr/lib/vmware/messages/es/vmware-mks.vmsg".

(vmware-tray:18948): Gdk-WARNING **: 03:47:29.104: The program 'vmware-tray' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 521 error_code 2 request_code 135 (XKEYBOARD) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

Please let me know if I may help testing.

denji commented on 2025-12-28 03:41 (UTC)

@xuan880 https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/293

xuan880 commented on 2025-12-27 15:59 (UTC)

During use, the software crashed and displayed the following error. You may try downgrading the gstreamer and gst-plugins-base packages to version 1.26.9.

vmware-tray[4255]: The program 'vmware-tray' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 334 error_code 2 request_code 135 (XKEYBOARD) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

vmware[4099]: The program 'vmware' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 79654 error_code 2 request_code 135 (XKEYBOARD) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

JulianXhokaxhiu commented on 2025-12-14 11:26 (UTC)

@kharovtobi: Unfortunately it's not up to me, that used to be included in workstation itself directly, now it is not available somehow nor on their CDN or in the package itself. If it will eventually show up I'll be happy to add it again.

kharovtobi commented on 2025-12-14 04:28 (UTC)

Can you add windows-x86.iso?