Win11 24H2 breaks iGPU UHD 770 sriov?

B

balthisar

New Member
Jan 29, 2024
9
1
3
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?
 
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.
 
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.
 
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.
 
So a fresh install of Windows is working? This issue only turns up if you're updating Windows that already had these features enabled?
 
Enabling any of those features results in Windows running as a VM in Hyper-V, and SR-IOV doesn't work at all with Hyper-V, both fresh install and upgrade install.

It's nice to have Windows Sandbox in Windows, but on the other hand, VM's under Proxmox are cheap and disposable, so I don't really need any of those features.
 
  • Like
Reactions: thatguyoverthere
balthisar said:
Enabling any of those features results in Windows running as a VM in Hyper-V, and SR-IOV doesn't work at all with Hyper-V, both fresh install and upgrade install.

It's nice to have Windows Sandbox in Windows, but on the other hand, VM's under Proxmox are cheap and disposable, so I don't really need any of those features.
Click to expand...
Wow thanks for getting back so fast, I wasn't sure if anyone would monitor this thread anymore.
 
No problem. I was at the keyboard when the email notification came in. Obviously not the same case as this response, though ;-)
 
Hello
i have the same problem, with the win11 24H2 update
a fresh installation work well but

i am also using SR-IOV to partition out my 13th Gen Intel iGPU
with Proxmox 8.2.2 or 8.3.0 server

i used the Derek Seaman Blog ,,GPU Passthrough,,
every thing worked well the last half year

but now with the Win 11 24H2 update i have big problems

after the Update from 24H2 the vm starts and every thing is OK

then when the VM is rebooted or shutdown and restarted the second time after the Update

the VM booting into Automatik Repair and thats it

i also encountered that after upgrading to Virt-IO Version ..262,, or ,,266,, the Guest Agent doesnt work anymore

i tryed the win11 24H2 Update on a Proxmox 8.2.2 and also on an Proxmox 8.3.0
on both the same beavior

,,Windows 11 version 24h2 enable virtualization for its security with VBS/HVCI,,
how can i check that??
 
You must log in or register to reply here.
Top Bottom