On 1/26/2025 at 9:03 AM, Kraizel said:

EDIT 2: One thing I have noticed is that after installing the plugin and passing through 1 VF to a vm the host doesn't go into sleep mode so I guess SR-IOV prevents sleep mode.

 

and you are aware NOT to go into s3 while a VM is running, especially while a pcie passthrough is active ...

this also goes for dGPU, PCIe Cards, ...

On 1/27/2025 at 8:58 PM, giganode said:

 

And what happens if you shut down the vm? Is it going to sleep then?

Hi, no it doesnt go into sleep either, I have checked multiple combinations and as long as I have the plugin installed and 7Vf detected (the default on my hardware intel N305) it does not go into sleep mode and actually freezes the system if I try to go into sleep. If I unninstall then plugin then sleep works again.

 

EDIT: I just checked again this morning, I installed the plugin, reboot the system, 7VF detected correctly and only 2 enabled by default, I didn't passthrough any vf yet and system cannot go into sleep, actually I had to hard reset as system froze after trying to go into sleep then I unistalled the plugin, reboot, now system goes into sleep as expected. Thanks

Edited January 29, 20251 yr by Kraizel

On 1/27/2025 at 9:05 PM, alturismo said:

and you are aware NOT to go into s3 while a VM is running, especially while a pcie passthrough is active ...

this also goes for dGPU, PCIe Cards, ...

yes of course, I meant when vm is not running or even without any vf passed through just with the plugin installed and vf correctly detected.

 

I guess some kernel parameter is preventing sleep when SR-IOV is enabled.

Edited January 29, 20251 yr by Kraizel

On 1/29/2025 at 11:19 AM, Kraizel said:

yes of course, I meant when vm is not running or even without any vf passed through just with the plugin installed and vf correctly detected.

 

I guess some kernel parameter is preventing sleep when SR-IOV is enabled.

 

I absolutely cannot recommend trying sleep mode. By design this makes no sense to me in combination with sriov.

On 4/7/2024 at 4:45 PM, giganode said:

 

You can use the iGPUs resources for VMs while unraid is also still able to use them, yes. 

 

Just connect via a service like sunshine/moonlight, parsec, rdp or vnc. If you need a physical monitor use an usb to hdmi dongle.

 

But keep in mind, this plugin relies on a repo which seems to be no longer maintained.

So don't just sell your gpu atm 😄

 

Once there is more information about the future of this plugin, it will be posted here.

 

Hi, may I check how do I get my VM output on a physical monitor using a USB to HDMI dongle?

15 hours ago, hoeman said:

 

Hi, may I check how do I get my VM output on a physical monitor using a USB to HDMI dongle?

If I had to guess.

 

Plug in the USB.

In the VM config check the box for the USB device to pass it through.

You may need to install the USB Dongle driver first via VNC / Remote desktop.

Edited February 17, 20251 yr by Raider_M

Hello everyone!

First of all thanks a lot for providing this awesome plugin!

 

I successfully use this plugin to provide a vgpu to my win11 VM.

Starting a game utilizes the GPU as expected.

I also wanna use sunshine/moonlight. I hope sunshine can use the vgpu to decode with h264/h265 or av1.

Since sunshine requires a connected display and I cannot "connect" a physical display to a vgpu using sr-iov, I was wondering if installing a virtual display does the trick.

What's required to use sunshine with the vgpu using sr-iov?

 

Advice is much appreciated!

 

CPU: i5 12400

GPU: UHD 730

3 hours ago, Jaytie said:

I also wanna use sunshine/moonlight. I hope sunshine can use the vgpu to decode with h264/h265 or av1.

 

encode mainly for sunshine 

 

3 hours ago, Jaytie said:

Since sunshine requires a connected display and I cannot "connect" a physical display to a vgpu using sr-iov, I was wondering if installing a virtual display does the trick.

What's required to use sunshine with the vgpu using sr-iov?

 

working fine here, but i would recommend parsec for sr-iov instead, a little better performing (here atleast) with low performance iGPU streaming, but just may test it side by side in your case.

6 hours ago, alturismo said:

encode mainly for sunshine

right 🙃

 

6 hours ago, alturismo said:

working fine here

So are you using an IddSampleDriver instead of dummy plug?

 

6 hours ago, alturismo said:

but just may test it side by side in your case

will do that!

 

Thank you!

1 hour ago, Jaytie said:

So are you using an IddSampleDriver instead of dummy plug?

 

there is nothing to plug for a vgpu  but actually i do have a KVM plugged in the HDMI port too ...

 

when i remember correctly, thats the one i use

 

https://github.com/VirtualDisplay/Virtual-Display-Driver

6 hours ago, alturismo said:

when i remember correctly, thats the one i use

 

https://github.com/VirtualDisplay/Virtual-Display-Driver

Yes I use the same one. 

Got it working, kind of. Normal Desktop Mode works while encoding with h.265. 

But when starting a game theres only sound and a blank white/black screen. All other virtual displays are disabled. 

It's weird because it works while on desktop but every game I have tested has no picture (windowed or fullscreen) but uses the vgpu as expected...

 

I'm still struggling here and I'm also not quite sure if this problem is related to SR-IOV. But I was able to pinpoint it litte further. It doesn't matter what software I use (Parsec, Sunshine/Moonlight, RDP).

So for example Sunshine/Moonlight:

I create a virtual display with VDD which is used by sunshine. I connect with moonlight and so far everything works and sunshine uses the virtual iGPU (00:02.1) to encode the stream. (I can see it is utilized)

The problems starts when I try to launch a game, which uses the iGPU too. Game is running but without picture. 

 

When I go to Windows/Settings/Display/Graphics and assign "GPU2: Microsoft Basic Render Driver" to that game, it works, but with unusable performance obviously.

 

So it seems like, when sunshine + game use the iGPU there no picture (the game still utilizes the iGPU, though).

 

Is this expected? 

I'm stuck. Can someone help here?

 

edit:

Well, I think I can confirm now, that this has nothing to do with SR-IOV. After almost two days of digging, I started from scratch and checked some things that I thought are already fine:

 

I deinstalled and Intel GPU driver and installed the most recent one and couldn't believe it, but now it seems to work. 

So ist was a driver problem all along. Well, lesson learned i guess.

Edited February 20, 20251 yr by Jaytie

1 hour ago, Jaytie said:

So ist was a driver problem all along. Well, lesson learned i guess.

glad to hear, may drop a short note when you cross tested sunshine, moonlight vs. parsec ... just out of interest here.

21 hours ago, alturismo said:

glad to hear, may drop a short note when you cross tested sunshine, moonlight vs. parsec ... just out of interest here.

 

All I did was a short test in order to find out, if my problem was sunshine related. No tweaking done or anything. That said, Parsec was a little bit stuttery. Quite happy with Sunshine and Moonlight right now. Since it's open source, I also prefer it.

 

But I might have to do another test, since I'm running the newest drivers now.

2 hours ago, Jaytie said:

Quite happy with Sunshine and Moonlight right now. Since it's open source, I also prefer it.

thanks for the feedback, here its vice vers  thats why i personally always recommend parsec for these VM's ...

 

not for a Gaming VM with an Nvidia Card or so, there moonlight and co is always the better choice

any news for SR-IOV working on 14gen intel cpu? / some time ago i readed something about new kernel is nessesary or patches  - still get error, that the sr-iov device disapears after some minutes and need to reboot whole server bcs gpu is gone.

 

 

Does this work with machine type i440fx or does it have to be Q35?

4 hours ago, Di4rnu said:

Does this work with machine type i440fx or does it have to be Q35?

i440fx is a legacy option for backwards compatibility and doesn't have a native PCIe bus, so I'd recommend using Q35. 

Just wanted to mention. Switching from i440fx to Q35 fixed it for me. unraid 7.0.0, Intel i5-14400, native Windows drivers. Read just about this entire topic, very happy with the previous comment

Edited February 24, 20251 yr by Orion676

Very wierd behaviour. 

My VM running Blue Iris hosted on Unraid with the plugin installed was working perfectly.

CPU: 13100 i3. UHD 730 was showing up in Task Manager perfectly.

 

Then the VM stopped booting so I created a new one.

However, the new one is showing Error 43 in the Device manager.

 

I have a screenshot of the old config and the new one.

 

Could someone please help me troubleshoot?

Old Config:

 

 

New config:

 

6 hours ago, snz said:

Very wierd behaviour. 

My VM running Blue Iris hosted on Unraid with the plugin installed was working perfectly.

CPU: 13100 i3. UHD 730 was showing up in Task Manager perfectly.

 

Then the VM stopped booting so I created a new one.

However, the new one is showing Error 43 in the Device manager.

 

I have a screenshot of the old config and the new one.

 

Could someone please help me troubleshoot?

Old Config:

 

 

New config:

 

Update: I shut down the VM

Uninstalled the plugin

rebooted the server

reinstalled the plug in

set the virtual card number to one.

restarted the server..

reassigned the virtual GPU and still no success.

 

any help would be appreciated.

attaching screenshot of the error I am facing.

 

as well as a screenshot of how it looked before I assume the vdisk got corrupted not allowing me to boot from it.

 

On 8/2/2024 at 11:23 PM, nyavana said:

Issue: iGPU show code 43 error after enabling <feature policy='disable' name='hypervisor'/> in xml file

 

System:

Unraid 6.12.11, Windows 11 23h2

i5-13500 with b660 motherboard (enabled both iGPU and dGPU)

1st GPU: RTX 4070ti super (Primary, with display attached)

2nd GPU: Intel UHD 770 (Only used for codec)

 

Description:

It worked perfectly until I need to hide VM status on windows to play certain games that detect VM. 

I followed this guide https://forums.unraid.net/topic/127639-easy-anti-cheat-launch-error-cannot-run-under-virtual-machine/

However, as soon as I add <feature policy='disable' name='hypervisor'/>, iGPU disappear from task manager, show code 43, and can not be used anymore.

I use iGPU for OBS video capture encoding, and the primary nvidia gpu is not affected and still work. 

 

Things I tried:

1. Disable and re-enable iGPU stop code 43 on device manager, but iGPU still won't show on task manager and I can not use the iGPU. Do a restart, and code 43 will appear again.

2. Change to a different vGPU (02.3 to 02.4) does not work

3. Delete <feature policy='disable' name='hypervisor'/> from xml will allow iGPU to work again, but I need that line.

4. Upgrading intel gpu driver from windows update does not resolve it

5. I don't see any error on vm log

6. Updating unraid from 6.12.10 to 11 does not resolve it.

Thank you so much for posting this!!! You helped solve the issue of the Error 43 I was having above!

please renew for unraid 7.0.thank you 

2 hours ago, doudou1234 said:

please renew for unraid 7.0.thank you 

is automatically done and working

After upgrading to 7.0.1, I get this all the time for all virtual adapters:

 

Mar 5 20:47:11 nas kernel: i915 0000:00:02.2: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.17 (0000000000000000) Mar 5 20:47:11 nas kernel: i915 0000:00:02.2: [drm] *ERROR* GT0: IOV: Found interface version 0.1.17.0 Mar 5 20:47:11 nas kernel: i915 0000:00:02.2: [drm] *ERROR* GT0: IOV: Unable to confirm version 1.17 (0000000000000000) Mar 5 20:47:11 nas kernel: i915 0000:00:02.2: [drm] *ERROR* GT0: IOV: Found interface version 0.1.17.0

 

looks like a semantic error to me. Isn’t 1.17 equal to 0.1.17.0?

 

Code 43 reappeared in my VM and I cannot get it working anymore. Is this expected behavior after updates? Checken the intel sr-iov plugin. There’s no update. Tried reinstalling and rebooting but no change in behavior. Any thoughts?