May 19May 19 I understand that much. Perhaps I didn't express myself clearly. It's just that in version 7.3.0, a new feature was added allowing you to change the number of VFs under "PCI Devices and IOMMU Groups" as well. Now there are two places where I can modify these settings:Settings --> Intel Graphics SR-IOVDo you see what I mean now?
May 22May 22 After updating to 7.3.0, I found that the virtual graphics card generated by SR IoV can be used for Windows 11, but cannot be used for FNOS. Now I have rolled back to 7.2.4
May 22May 22 will this work now on 7.3 with i5 14500 ?if i passtrough it to my windows guest, i can install the intel display driver, devicemanager shows all ok, but parsec still uses software renderer and can run furmark etc.edit:ok, worked, but my whole igpu crashs after VM shutdown .. need to do : echo 1 > /sys/bus/pci/rescanin unraid shell + add VFs back (no restart nessesary , worked again after)but after each VM reboot / shutdown, the igpu crashs and i need rescan and readd the VFs, any solution for this? Edited May 22May 22 by Encore
June 11Jun 11 Hi, kinda noob and everything is working but I just wanted to ask about the version. I installed the plugin from unraid CA and the version is 2023.11.22 and that shows as up-to-date, but the github itself has versions newer than that. How come this is the case?
June 11Jun 11 1 hour ago, hoeman said:Hi, kinda noob and everything is working but I just wanted to ask about the version. I installed the plugin from unraid CA and the version is 2023.11.22 and that shows as up-to-date, but the github itself has versions newer than that. How come this is the case?im not sure where you looked but its certainly 2023.11.22https://raw.githubusercontent.com/giganode/unraid-i915-sriov/refs/heads/master/i915-sriov.plg
July 1Jul 1 Hi, I'm not sure if this is the right place but I'm wondering if someone can either explain or direct me to a page that explains how to get SR-IOV working with the Intel 285k iGPU to pass a VF through to a VM.I've looked around but the information is conflicting, am I supposed to use the Xe driver or can I still use i915? Am I still supposed to use this plugin as well? Is it even possible right now (the posts seemed to imply the kernel would support it early 2026 but haven't heard anything since). Any help with the latest info on this would be greatly appreciated.
July 6Jul 6 I have never been successful at getting a linux guest to successfully pass through a VF.I am trying again, because I really need access to the i915 graphics to run frigate.using cachyos (arch) as a guest... and tried a few things to get it going... but errors out like this:If you've managed to overcome something similar I would appreciate some steps to try. googling has not really helped me.I am running latest unraid... with sriov plugin installed and working. Win11 VM is able to work with this... but linux guests must have a secret sauce I am not aware of....>2026-07-06T10:43:13.649353Z qemu-system-x86_64: warning: vfio_container_dma_map(0x151aa730be00, 0x382820000000, 0x108000, 0x151a9f000000) = -22 (Invalid argument)0000:00:02.1: PCI peer-to-peer transactions on BARs are not supported.>
July 6Jul 6 @bucky2780 the sr-iov dkms module must be installed on Unraid and inside the guest. In addition all the apps in the guest(think the desktop environment, Plex, jellyfin, frigate) must run as a user with permission to access the gpu. This is not always the case and you must always check that the dkms module is installed and running without errors on the host (Unraid) and the guest and the relevant users have permission to use the gpu in the guest. It took me months to figure out those two things for Linux guests, windows just works out the box
July 6Jul 6 ok interesting... I don't mind spending months trying to get this to work....but on a recent cachyos vm install... here is what I get when I add a vf as graphics device....I did install dkms on the guest... though I'm surprised that would be needed.mystery abounds...[ 5.144395] i915 0000:06:00.0: [drm] Found alderlake_s/raptorlake_s (device ID a780) integrated display version 12.00 stepping D0 [ 5.226777] intel_rapl_msr: PL4 support detected (updated). [ 5.315093] systemd-journald[258]: Received client request to flush runtime journal. [ 7.146092] i915 0000:06:00.0: [drm] ERROR Device is non-operational; MMIO access returns 0xFFFFFFFF! [ 7.146399] i915 0000:06:00.0: [drm] ERROR Device initialization failed (-5) [ 7.146402] i915 0000:06:00.0: probe with driver i915 failed with error -5
July 10Jul 10 I recently installed/uninstalled the sr-iov plugin... to ensure it works as it is supposed to...I do get these worrying error messages every time I reboot unraid... particularly the segfault in igpu_top is a little worrying.The plugin does seem to work... but my system is a litlte unstable... What do you think about these error messages ? Benign or not ?>>Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE0000102Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF1 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE0000102Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF2 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE000000AJul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF3 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE000000AJul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF4 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE000000AJul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF5 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE000000AJul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF6 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE000000AJul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF7 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: intel_gpu_top[36393]: segfault at 78 ip 000055919e3d1464 sp 00007ffc43596790 error 4 in intel_gpu_top[9464,55919e3ce000+a000] likely on CPU 12 (core 24, socket 0)Jul 11 05:57:02 buckyu kernel: Code: ff 4c 8b bd 98 e4 ff ff 48 89 b5 f0 e9 ff ff 48 89 bd f8 e9 ff ff eb 12 4c 89 f8 48 83 c0 08 49 89 c7 48 8b 00 48 85 c0 74 11 <80> 78 38 00 74 e8 48 8b 78 30 e8 5d d2 ff ff eb dd 48 8b 85 70 e4>>
July 27Jul 27 On 7/11/2026 at 7:24 AM, bucky2780 said:I recently installed/uninstalled the sr-iov plugin... to ensure it works as it is supposed to...I do get these worrying error messages every time I reboot unraid... particularly the segfault in igpu_top is a little worrying.The plugin does seem to work... but my system is a litlte unstable...What do you think about these error messages ? Benign or not ?>>Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE0000102Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save VF1 state (-EPROTO)Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] ERROR GT0: GUC: CT: Sending action 0x550b failed (-EIO) status=0XE0000102Jul 11 05:57:02 buckyu kernel: i915 0000:00:02.0: [drm] GT0: IOV: Failed to save >>In response to my earlier post, I am pleased to confirm I got the sriov plugin to cleanly install in my unraid system. Sharing it here, since it may help someone else.After tearing my hair out, I checked back into the Asrock Rack bios, and sure enough I found an additional parameter that said something like "start SR-IOV at boot". I ticked this and that seemed to do the trick.This is in addition to the normal SR-IOV option which was already ticked.Live an learn.>>BTW, still unable to get a cachyos guest to cleanly use the VF. I get some horrible errors in dmesg, despite having installed via the aur the dkms sriov package.If anyone here has been able to get their cachyos to cooperate, would appreciate on how to get that done. Do I need to blacklist the xe driver? i915 driver ? What ?
July 30Jul 30 Just a heads up for Unraid 7.2.8 and SR-IOV users.SRIOV currently doesn't compile against Kernel 6.12.98 which Unraid 7.2.8 is based on, so to speak, don't upgrade if you need SRIOV support.An issue was already opened in their GitHub but I think they are a bit exhausted supporting that many Kernel versions and it will take time to be updated so that it works again.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.