41 minutes ago, giganode said:

keep in mind that this plugin is soon to be not working anymore with future OS/Kernel updates. There is quite some work to be done.

 

In theory it should "just work" once the new Intel drivers are ready for production use, assuming the new drivers support your Intel GPU.

 

This is from Intel's announcement:

Quote

SR-IOV Platforms
================

Initially we plan to add SR-IOV functionality to the following SDV platforms
already supported by the Xe driver:

 - TGL (up to 7 VFs)
 - ADL (up to 7 VFs)
 - MTL (up to 7 VFs)
 - ATSM (up to 31 VFs)
 - PVC (up to 63 VFs)

Newer platforms will be supported later, but we hope that enabling will be
much faster, as majority of the driver changes are either platform agnostic
or are similar between earlier platforms (hence we start with SDVs).
 

 

 

Those platforms are Tiger Lake, Alder Lake, Meteor Lake, Arctic Sound M, and Ponte Vecchio respectively.

 

 

Edited September 16, 20241 yr by Daniel15

49 minutes ago, ars92 said:

Just to confirm, SR IOV doesn't make it possible to use the iGPU with Docker containers (example Plex for HW transcoding) and also multiple VMs passthrough, at the same time correct? We have to choose either one?

SR-IOV lets you split the iGPU up to seven ways. Either the host (for Docker) + 6 VMs, or 7 VMs if you don't use the GPU on the host.

5 hours ago, Daniel15 said:

SR-IOV lets you split the iGPU up to seven ways. Either the host (for Docker) + 6 VMs, or 7 VMs if you don't use the GPU on the host.

 

No, the VFs are for virtual machines. So 7 VFs can be used on 7 VMs simultaneously.

On 9/16/2024 at 11:44 AM, Daniel15 said:

 

In theory it should "just work" once the new Intel drivers are ready for production use, assuming the new drivers support your Intel GPU.

 

This is from Intel's announcement:

 

Those platforms are Tiger Lake, Alder Lake, Meteor Lake, Arctic Sound M, and Ponte Vecchio respectively.

 

 

So intel will support 12th gen alder lake but not 13th & 14th gen raptor lake?

Or will 13th & 14th be supported because they essentially have the same iGPU?

41 minutes ago, mans_ said:

So intel will support 12th gen alder lake but not 13th & 14th gen raptor lake?

Or will 13th & 14th be supported because they essentially have the same iGPU?

They said "newer platforms will be supported later". 

On 9/29/2024 at 7:48 PM, Daniel15 said:

They said "newer platforms will be supported later". 

13th Gen Intel® Core™ i9-13900K working fine over here.

6 minutes ago, letrain said:

13th Gen Intel® Core™ i9-13900K working fine over here.

With the Xe driver (which won't need any plugin), or with the i915 driver (which is the one this plugin is for)? The conversation above was about the Xe driver specifically.

Edited October 4, 20241 yr by Daniel15

I think I have found the bug. Every time I stop the VM that uses VF the whole iGPU is removed from the system

dmesg:

Oct  5 22:20:08 Unraid kernel: i915 0000:00:02.0: VF1 FLR
Oct  5 22:20:11 Unraid kernel: vfio-pci 0000:00:02.1: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 22:20:11 Unraid kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem
Oct  5 22:20:11 Unraid kernel: vfio-pci 0000:00:02.2: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 22:20:11 Unraid kernel: vfio-pci 0000:00:02.3: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 22:20:11 Unraid kernel: pci 0000:00:02.1: Removing from iommu group 24
Oct  5 22:20:11 Unraid kernel: vfio-pci 0000:00:02.2: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 22:20:11 Unraid kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem
Oct  5 22:20:11 Unraid kernel: vfio-pci 0000:00:02.3: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 22:20:11 Unraid kernel: pci 0000:00:02.2: Removing from iommu group 25
Oct  5 22:20:11 Unraid kernel: vfio-pci 0000:00:02.3: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 22:20:11 Unraid kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=io+mem:owns=io+mem
Oct  5 22:20:11 Unraid kernel: pci 0000:00:02.3: Removing from iommu group 26
Oct  5 22:20:12 Unraid kernel: i915 0000:00:02.0: Disabled 3 VFs
Oct  5 22:20:12 Unraid acpid: input device has been disconnected, fd 10
Oct  5 22:20:13 Unraid kernel: pci 0000:00:02.0: Removing from iommu group 0

 

Then the lspci doesn't show the iGPU at all.

The way to bring it back (other than reboot) is to force the pci rescan

echo 1 > /sys/bus/pci/rescan

 

It brings back main iGPU but not VFs. I need to go back to settings and re-enable VFs then it starts to work again and only then I can run VM again. I'm using it on N100 if it matters.

FYI, this plugin broke for me on v7-beta3
Suggest waiting for an update to the plugin before upgrading, I had to roll back.

6 hours ago, Vit01 said:

It brings back main iGPU but not VFs.

If you're reinitializing the card, you also need to re-enable SR-IOV:

 

echo 7 > /sys/devices/pci0000:00/0000:00:02.0/sriov_numvfs

 

Before doing that, double-check the address (00:02:0) in lspci output and adjust it if needed.

Edited October 6, 20241 yr by Daniel15

5 minutes ago, Raider_M said:

FYI, this plugin broke for me on v7-beta3
Suggest waiting for an update to the plugin before upgrading, I had to roll back.

What kernel version does beta3 use, and which version did the previous beta use?

2 hours ago, Raider_M said:

FYI, this plugin broke for me on v7-beta3
Suggest waiting for an update to the plugin before upgrading, I had to roll back.

 

Interesting. Do you have any more information?

 

@alturismo already verified the plugin running on 7.0.0-beta.3.

 

I just updated yesterday evening without any issue but couldn't test anymore cause it was way too late.

can confirm, working as expected

 

3 hours ago, Daniel15 said:

What kernel version does beta3 use, and which version did the previous beta use?

 

beta3

root@AlsServerII:~# uname -a
Linux AlsServerII 6.6.52-Unraid #2 SMP PREEMPT_DYNAMIC Fri Sep 27 10:05:59 PDT 2024 x86_64 Intel(R) N100 GenuineIntel GNU/Linux
root@AlsServerII:~#

 

Yea so the plugin would not load for me.
I have i5-13500

Updated Unraid through GUI etc as normally would.
It shot me an error in my notifications about the plugin, which I irgnored then reboot.
Watching CLI on boot it said something about i915 not loading, also might have said something about modprobe
When unraid loaded, the plugin was missing and I could not install it - reporing an error while trying to install.

I did not take notes of the terminal errors at the time, but I have a few logs in syslog right after first boot of beta3

Downgraded to beta2 and the pluging installed again without issue.
I won't have the capability to try upgrade again for a few days. I would take more notes then.

Beta2 for me now:
uname -a
Linux Tower 6.8.12-Unraid #3 SMP PREEMPT_DYNAMIC Tue Jun 18 07:52:57 PDT 2024 x86_64 13th Gen Intel(R) Core(TM) i5-13500 GenuineIntel GNU/Linux


 

Quote

Oct  5 14:10:44 Tower kernel: i915 0000:00:02.0: VF1 FLR
Oct  5 14:10:44 Tower kernel: vfio-pci 0000:00:02.1: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none
Oct  5 14:10:44 Tower kernel: xe 0000:00:02.1: Your graphics device 4680 is not officially supported
Oct  5 14:10:44 Tower kernel: by xe driver in this kernel version. To force Xe probe,
Oct  5 14:10:44 Tower kernel: use xe.force_probe='4680' and i915.force_probe='!4680'
Oct  5 14:10:44 Tower kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4680' and
Oct  5 14:10:44 Tower kernel: CONFIG_DRM_I915_FORCE_PROBE='!4680' configuration options.
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: Running in SR-IOV VF mode
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: [drm] GT0: GUC: interface version 0.1.9.0
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: [drm] VT-d active for gfx access
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: [drm] Using Transparent Hugepages
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: [drm] GT0: GUC: interface version 0.1.9.0
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: GuC firmware PRELOADED version 1.9 submission:SR-IOV VF
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: HuC firmware PRELOADED
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: [drm] Protected Xe Path (PXP) protected content support initialized
Oct  5 14:10:44 Tower kernel: i915 0000:00:02.1: [drm] PMU not supported for this GPU.
Oct  5 14:10:44 Tower kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.1 on minor 1

 

Edited October 6, 20241 yr by Raider_M

22 hours ago, Daniel15 said:

If you're reinitializing the card, you also need to re-enable SR-IOV:

 

echo 7 > /sys/devices/pci0000:00/0000:00:02.0/sriov_numvfs

 

Before doing that, double-check the address (00:02:0) in lspci output and adjust it if needed.

The thing is I don't want to reinitialize the card, Unraid forces me to do so as closing VM means iGPU is gone. The expected behaviour is iGPU stays in place and I can run another or the same VM.

On 7/16/2024 at 2:13 PM, Raider_M said:

Hey @bucky2076

Just wondering if you (or anyone else) ever had any luck getting the intel i915 drivers loaded in Linux?
I too am having issues and have had no luck getting the card to initiate properly in a Linux VM
Works flawlessly on my dockers and windows VM.
Does does not want to show in /dev/dri and on boot get errors etc.

I am trying to get an instance of nextcloud aio vm up and running and want to pass through a VF for some transcoding purposes.
I may need to revert back to docker for this. Not the biggest issue but would prefer to have it inside a VM.

sorry but no... I parked it, and am waiting for newer xe drivers for linux. That should improve things.

Seems like the Xe driver being part of the kernel is now planned for kernel 6.13 which may release around February 2025. And not sure when will unRAID support 6.13 as its now bound by the supported kernels by ZFS.

 

https://github.com/intel/linux-intel-lts/issues/33

 

 

Hopefully we will have native Xe SR IOV support in unRAID for 14th gen Intel by mid next year, but a lot of things needs to fall in place for that to happen  

Hello, trying to understand why my Arc cards and IGPU not working in Unraid

Not sure if this related - but SR-IOV blacklist i915, can this be a case?

And why it blacklists igpu?

I have core ulta cpu

3 hours ago, J05u said:

Hello, trying to understand why my Arc cards and IGPU not working in Unraid

Not sure if this related - but SR-IOV blacklist i915, can this be a case?

And why it blacklists igpu?

I have core ulta cpu

Are you using the sriov driver as this is different to core i915. Arc does not support sriov. If you are not virtualising the igpu remove sriov plugin and reboot.

4 minutes ago, SimonF said:

Are you using the sriov driver as this is different to core i915. Arc does not support sriov. If you are not virtualising the igpu remove sriov plugin and reboot.

yeah, I understand about arc, I was thinking that igpu on core ultra can be splitted for plex, and arc cards I wanted to use with Tdarr, but In the end in gpu top gpu is in the list, in gpu top  -l, not, I don't understand latest intel generation

42 minutes ago, J05u said:

yeah, I understand about arc, I was thinking that igpu on core ultra can be splitted for plex, and arc cards I wanted to use with Tdarr, but In the end in gpu top gpu is in the list, in gpu top  -l, not, I don't understand latest intel generation

New CPUs will need the XE driver which is replacing i915. Not in current kernels. Needs > 6.8 when it was first added but would need to be min 6.12 I think for stable.

Thank you, so it means igpu not working for unraid?

Or just sr iov?

 

1 hour ago, J05u said:

Thank you, so it means igpu not working for unraid?

 

not yet as the kernel doesnt support it yet as supposed to ...

 

On 12/2/2024 at 9:42 PM, J05u said:

can be splitted for plex

you dont need sr iov for plex anyhow ... no vgpu's needed therefore while using dockers, sr iov vgpu's would be something for using it in a VM and not in a docker ...

 

1 hour ago, J05u said:

Or just sr iov?

as stated above, not yet as the driver is not ready / there ... in the kernel (xe driver), and once it will be ready for the new core cpu's igpu's ... then sr iov would prolly need some updates too and we will see if its coming or not.

 

in sum, your CPU is yet not supported by the kernel version Unraid is running on for sr-iov and about general usage i cant tell, for my knowledge it should already be supported on v7 rc1 as it uses kernel 6.6 which already should also support core cpu igpu's

 

 

but @SimonF can prolly say for sure if iGPU Docker support is already given in v7 or not

This plugin does not seem to work on 7.0.0-rc.1. In the release notes of 7.0.0-rc.1 it does mention:

 

Add/edit VM template

• Add SR-IOV support for Intel iGPU

So maybe it's supported natively and not needing the plugin? I can't seem to figure it out.

 

If I keep the plugin installed Unraid pretty much locks up when the array is started. If I remove the plugin it boots fine and everything works fine, but obviously I cant use SR-IOV with my iGPU. Was working fine on beta 2 of 7.0.0.

4 hours ago, PaulW08 said:

This plugin does not seem to work on 7.0.0-rc.1. In the release notes of 7.0.0-rc.1 it does mention:

 

Add/edit VM template

• Add SR-IOV support for Intel iGPU

So maybe it's supported natively and not needing the plugin? I can't seem to figure it out.

 

If I keep the plugin installed Unraid pretty much locks up when the array is started. If I remove the plugin it boots fine and everything works fine, but obviously I cant use SR-IOV with my iGPU. Was working fine on beta 2 of 7.0.0.

 

The plugin is verified to work under rc1. You may have a different problem. Can you provide more details?