VMware Player: No 3d support available from the host

vmwp-no3d-avail.md

VMware Player: "No 3d support is available from the host"

NOTE: I no longer use VMware products, and on good authority this trick no longer works (see comments below).

Facts: VMware Player on Ubuntu 18.04 LTS with the standard Gnome desktop running an AMD WX-2100 graphics card. Both glxinfo and glxgears show 3d acceleration is enabled and working on the host. In addition to VMware Player, the host is also running the qemu-kvm/libvirtd stack from Ubuntu's official repositories. My use case for 3d accelerated graphics in a Windows guest is to occasionally play a Windows-only game.

Issue: Player barks this warning during installation of... anything.

Solution: This askubuntu post, Powered by StackExchange[TM], provides the solution:

1. Make sure 3d graphics is enabled in the guest settings and VMware Tools installed in it.

2. Shut down the Windows VM and exit Player.

3. Edit ~/.vmware/preferences to add...

mks.gl.allowBlacklistedDrivers = "TRUE"

4. Start up the guest VM in Player.

NOTES:

1. Why not use qemu-kvm instead of VMware Player? Because there isn't a working Windows driver for virtual 3d accelerated graphics. The virGL project had this as a goal around five years ago (back when I went all-in on qemu-kvm myself), but has yet to deliver for Windows guests.

2. Why not PCI (VFIO) pass-through? Too expensive for me, and I suspect for most ordinary users. If you need 3d graphics on Windows, it's probably justifiable. But then you could put the same money into a second workstation running Windows on bare metal. There's still a frustratingly high learning curve for getting pass-through graphics up and running, and the premium hardware required is very expensive (high-end motherboard and two graphics cards, as well as a spare monitor or a pro KVM switch -- like a Blackbox for reliability and durability).

3. You can't run a VMware and a qemu-kvm guest at the same time, each virtualization system wants exclusive access to the kernel. For desktop use that shouldn't be a problem, but if the host doubles as a virtual lab (as mine does) you're going to have to shut down all your qemu-kvm guests before launching a guest in Player. It's an annoyance, but manageable for me. Note that you do not have to shut down or recycle libvirtd before or after using VMware Player.

you should use older version of VMware or ( lite version) It will solve the problem.

I wished that you didn't necro this thread. Downgrading to a older version of VMware will not always solve problems.

I just got this issue on my VMware installation after the 25H2 update (Yes, they genuinely changed the versioning scheme to match Windows 11). Adding the said configuration doesn't cut it anymore.

Sadly, not surprised. I'm afraid that continuous regression is what we can expect from here on out. I've abandoned VMware at this point. Qemu/kvm's implementation of 3d accel (still Linux only) is persistently disappointing. I've now got an old Thinkpad running Windows to fill the gap. Even the iGPU in an i5-6500 beats any existing emulation. Most of my efforts nowadays are focused on eliminating the need for Windows in my personal life. The trajectory MSFT is on already made that inevitable. Being able to run Windows VMs was always a convenience that benefited my employers more than me. After 30 years at this, I'm ready to move on.

I have a solution for the 25H2 update. Your host machine must support and have Vulkan installed because the vmware virtual machines require it for 3d support from now on. It also may help (after Vulkan is installed) to open the .vmx file (with a text editor) in your virtual machine folder to add this line:
mks.vk.allowUnsupportedDevices = "TRUE"
then save the change. Make sure when you do the edit that the VM has been fully shut down.
I don't think Broadcom/Vmware announced this change which I'm sure frustrated alot of people who thought they still could get by with having Opengl without needing Vulkan.