Win11 24H2 breaks iGPU UHD 770 sriov?

[balthisar]

Good day,

I've been using SR-IOV to partition out my 13th Gen Intel iGPU to various VM's, and it's been working swell, even with Windows 11. Although I access it via RMD, it still uses the iGPU for rendering, which is nice.

Today I got the 24H2 update for Windows 11, and now I'm getting error 43. Drivers are up to date, etc, and I'm on Proxmox VE 8.2.2

Has anyone else encountered this issue on Windows when updating to this newest release? Is there a quick fix?

A further wrinkle is, I recently upgraded from a 13th gen i3 with UHD 730 graphics to the 13-1/2 gen i7 with UHD 770. I didn't recompile anything – all my Linux VM's still access their SR-IOV passthrough successfully for encoding, etc., and Windows 11 did prior to today's 24H2 update. It's possible that Windows 24H2 is more sensitive to any iGPU changes than previous versions? I'm not really seeing anything in the high level commit messages for i915-sriov-dkms that make me think I'd need an updated version.

So, anyone been down this road and found a solution?

 

[balthisar]

Just confirming that a fresh install of Windows 11 23H2 has my SR-IOV slice working quite nicely. This seems to be a Windows 11 specific issue for 24H2.

 

[balthisar]

I hate spamming myself, but updating the new image to 24H2 still gives me a working VF. This is getting to become quite the investigation.

 

[balthisar]

Ok, it's not related to 24H2 at all. Apparently it's the enabling of any type of Hyper V feature that kills the virtual functions: Sandbox, WSL2, Hyper V proper. I don't really need any of those features, I suppose.