I also got this 3D incompatibility message on my host system (Ryzen 5800H), but still the "Accelerate 3D graphics" option was enabled for all VMs! As mentioned, this causes my VMs to freeze (not accepting any mouse or keyboard input or updating the display, but still "running") when they are idle for some time or locked. Disabling the option solved the problem, but that's not a good solution of course, because it disables some visual effects in the guest OSes...
Original Message:
Sent: Sep 20, 2024 11:45 AM
From: Joe Goldthwaite
Subject: I don't recommend updating to Vmware Workstation 17.6 for multiple monitor VMs.
That's a good suggestion!
At this point I downgraded to 17.0.2 so I can no longer test it. I don't think that's it though. On the Ryzen machine I would get a message when starting the VM that the host computer didn't have support for 3D acceleration. I would think that would in effect disable it. So I had the same issue on an nvidia based system and an amdgpu based system.
The one thing I do know is that it's only happened to me on 17.6.
If I decide to try and upgrade to 17.6 again I'll test it.
Original Message:
Sent: Sep 19, 2024 02:56 PM
From: FCrane
Subject: I don't recommend updating to Vmware Workstation 17.6 for multiple monitor VMs.
Try disabling "Accelerate 3D graphics" in the "Display" options of the VM Settings. This solves the problem with freezing VMs when locking or idling - maybe it also solves your freezes.. You loose some graphics effects (like rounded corners of dialogs in Windows 11 guest systems) though.
There's obviously some serious bug with the graphics driver, which was introduced in v7.6, because it never happened on previous versions.
Regards!
Original Message:
Sent: Sep 17, 2024 03:22 PM
From: Joe Goldthwaite
Subject: I don't recommend updating to Vmware Workstation 17.6 for multiple monitor VMs.
There's a pretty sever bug.
I have three 4k displays. I normally have one display for my Linux Mint host and use two others for a Windows virtual machine. This has worked fine for years but something broke with 17.6. The primary display works fine but Vmware doesn't understand that the second display also belongs to the VM.
I noticed it because as soon as any Windows application was moved to the second display it became unresponsive to the mouse or keyboard. It's really easy to see. I have a different mouse cursor in Windows vs the host. As soon as I move the mouse to the second Windows display, the mouse cursor changes to the Mint cursor. Any attempts to click on programs are ignored. The VM does not receive any mouse or keyboard inputs.
I've had this happen on two different machines running on both Linux Mint 21.3 and Linux Mint 22. They both have Ryzen processors but on uses the amdgpu and the second is nvidia. All drivers were up to date.
There's a known issue with this release that says that some multi-monitor typologies have issues and there's no work around. I recommend skipping this release if you're trying to use two monitors with a VM.