I’ve observed that AMD GPU’s have an issue in their driver that causes a driver crash (sometimes an entire VM crash, or sometimes the AMD driver is able to reset the GPU and the VM continues to work).
I think I have narrowed down the issue to running a test that leverages mesh shaders (DX12 or Vulkan).
I’ve tested using an RX6600, RX6700XT and RX6800 and all have the same issue. Guest is Windows 11. Reinstalled the host a few times with different OS’s and the same result. Running an NVIDIA card passed through (RTX 2080) or running the AMD cards on bare metal on the same host run the tests without issues.
Can anyone with a passed through AMD card (RX 6xxx) run a mesh shader test for me and let me know if it runs or crashes? The best ones I’ve found are either the 3dmark mesh shader test or GravityMark and set the API to Vulkan or DX12 and renderer MS (mesh shader).
Posted this on reddit but didn’t get any replies from anyone with an RX6000 series card. Thanks!
I can try. Is there a way to run 3dmark without purchasing it? Otherwiae I’ll try gravity mark.
I have a RX6600 but its connected with pcie v3 4x. My system:
Host OS: Proxmox 7.2, KVM/qemu Hypervisor
CPU: Intel i9 9900K
RAM: 64GB DDR4
GPU1: nvidia geforce rtx 3080ti
GPU2: AMD RX 6600
HDDs: various SATA SSDs with zfs and 1x nvme 4TB
Thanks! I think the mesh shader test needs a licenced 3Dmark unfortunately, but gravity mark is free and for me the gravity mark tests fail every single time on both Vulkan and DX12 when using MS. As it’s loading the test, the driver crashes. Using the other renderers works without issues.
Yeah trying to determine if there’s something up with my hardware config or if this is an AMD issue. I’m getting crashes on Halo Infinite when using any driver from the last year and a half, and I suspect that it’s because Halo introduced MS in one of the updates and any AMD driver after the one that doesn’t crash added the APIs that halo is using.
It’s only a matter of time that more games start using mesh shaders, so if there is an issue would be good to start looking for a fix
Sorry, I was quite busy this week - but I updated the Windows VM and installed
the latest driver Radeon driver today in the morning, before I went to work. I’ll report back.
So I ran the benchamark, but only had the gravity mark on hand. The mesh shader crashed the GPU / GPU driver in Vulkan (~ the “Initializing 8.6s” mark) and in DX12 (~ the “Initializing 10.6s” mark) every time. The VM then had the “internal error state” in Proxmox, but could be stopped and restarted via the cli.
Output was stuck at the loading screen frame (and everything else which was displayed at this time) until the VM was restartet. The benchmark didn’t come close to rendering anything besides the loading screen with mesh shader enabled. Latest GPU driver tested. The VM / GPU driver didn’t recover itself after the crash.
(Sorry for the late reply, I was out of state due to a family matter)
So it seems confirmed mesh shader is buggy for passthrough use (?). I wonder how big an impact it’s outside gaming? And could it be fixed with a new driver and/or firmware?
Legend, thanks so much for testing this, basically rules out that it’s specific to my hardware.
It depends what is causing the crash, but I’ve found for one specific game (Halo Infinite), I get crashes on any driver past a 21.8.2. 21.8.2 and earlier drivers work perfectly fine, but 21.9.1 onwards and it crashes on the loading screen. Not sure if it’s using MS or another API that might also be bugged.
