Intel B50pro passthrough.

[ComfySofa]

Ah - sorry just so i understand (ReBar is enabled on mine?) - i only ask as whether the setting is off or on in native windows the intel windows driver says its not enabled.... (win for Proxmox if it is)!!

 

[uzumo]

I think it's probably enabled, but to be sure, launch it on Windows instead of PVE and check with GPU-Z.

GPU-Z can show whether Rebar is enabled.

 

[ComfySofa]

Ok - well im still stuck on the Code43 at the moment - so in the windows vm the intel suite cant see the card...

 

[uzumo]

Please try booting Windows on the host machine instead of a Windows VM.

If it shows as enabled in Windows, I don't think there's a difference in PVE, so I believe it should be enabled in PVE as well.

 

[ComfySofa]

Right well in that case no....no matter what the setting when windows is running native on the hardware no matter what the setting the intel graphics app says it disabled....as per that screenshot back at the start of the thread....that being said, ive not tried it since the proxmox side has been fixed....so i could plug the windows ssd back in and check tonight...

 

[uzumo]

If you're checking in PVE, you should be able to see it with `lspci -vvvs 0000:03`.

 

[ComfySofa]

Hmm - that just comes back with a prompt..?

 

[uzumo]

The prompt displays Rebar's functionality as shown in the image result, along with the current value.

Excerpt from my PVE's lspci -vvvs

Capabilities: [420 v1] Physical Resizable BAR
                BAR 2: current size: 16GB ★, supported: 256MB 512MB 1GB 2GB 4GB 8GB 16GB

This display, along with GPU-Z or HWinfo on my Windows VM showing the same values, should confirm this.

You can see that this matches the results shown in the images of GPU-Z and HWinfo on Windows above.

*Sorry for the awkward phrasing since it's a translation.

 

[ComfySofa]

Hi there. had a bit of a breakthrough for the strangest reason. I keep a, what i call, a base windows vm that i copy and then use for different jobs....this one was giving me the code 43 error....on the off chance i thought id create a fresh one...which works!!

And, i might add its not giving the rebar error - ive not put the windows ssd back in to see if its still an issue but thats not really something that bothers me as its staying as Proxmox.

So all i needed to do, is to create fresh VM's - which im going to do now.

Just for the info if i paste that command in i get an error saying the switch is wrong.

Finally just to thank you for sticking with me and getting me through it.! on the plus side totally unrelated ive been pushing to use ProxMox in my workplace for years (i work in IT) - you wouldnt have thought so after all this...but it looks like we're going to start using it.!