On 1/20/2025 at 9:16 PM, giganode said:

 

The experience is much better than with virtual graphics.

 

Exactly, sriov is the way to go. Also, this way you still can use the igpu in docker.

I am considering buying the following as a DisplayLink adapter:
https://plugable.com/products/usbc-6950u
 

However , it says that "We do not recommend or support our DisplayLink based graphics adapters with Linux at this time".

On this site where I can buy it, it says "Not compatible with MacOS, Linux/UNIX or ARM-based Windows."

 

Do you think it will work?

7 hours ago, Di4rnu said:

However , it says that "We do not recommend or support our DisplayLink based graphics adapters with Linux at this time".

 

then i wouldnt buy it for such a VM.

 

what VM would you like to use with sr-iov vgpu ?

 

EDIT: reading backwards, it was intended to use in win VM ... so is that still the case ? if yes, you pass the USB to your VM, so Win is the OS which will use it and should be fine, not the Host (Linux).

3 hours ago, alturismo said:

then i wouldnt buy it for such a VM.

 

what VM would you like to use with sr-iov vgpu ?

 

EDIT: reading backwards, it was intended to use in win VM ... so is that still the case ? if yes, you pass the USB to your VM, so Win is the OS which will use it and should be fine, not the Host (Linux).

Thanks for your reply!

 

Yes, I should have clarified that it is for Win10 or Win11 VMs. So it shouldn't matter that the host is Linux-based when it's passed through?

54 minutes ago, Di4rnu said:

Yes, I should have clarified that it is for Win10 or Win11 VMs. So it shouldn't matter that the host is Linux-based when it's passed through?

like already mentioned 1 post upper ... no need to clarify x times

 

4 hours ago, alturismo said:

if yes, you pass the USB to your VM, so Win is the OS which will use it and should be fine, not the Host (Linux).

 

Hi there, new here. I installed intel GPU TOP and then this SR-IOV plugin for my 12700K. I cannot get my VM to see the iGPU/UHD 770. I've installed the default Windows Update Intel display drivers and when I tried using the driver package from Intel's website I get an error saying I don't have any compatible devices. I don't have this issue when I bind the iGPU and fully passthrough it without the SR-IOV plugin and use a dummy HDMI cable - but I'd obviously like to have the VFs so I can do things like encode with Handbrake and have a VM with iGPU capabilities.

 

Here's my diagnostics and XML and some screenshots. Thank you!

yuzu-nas-diagnostics-20250307-0922.zip xml copy.txt

Quick question, What is the latest processor that supports this plugin?

According to Intel, 13th gen (Raptor Lake), 14th gen (Raptor Lake Refresh), and ultra 2 series (Arrow Lake) all supports SRIOV.

 

Background:

I am thinking about upgrading from 12700k to 265K as current motherboard can't support more ram.

If Arrow Lake is currently unsupported due to driver or kernel issue, where can I find the source so I can check progress myself?

Thanks in advance 

Edited March 7, 20251 yr by nyavana

On 3/7/2025 at 8:17 PM, nyavana said:

Quick question, What is the latest processor that supports this plugin?

According to Intel, 13th gen (Raptor Lake), 14th gen (Raptor Lake Refresh), and ultra 2 series (Arrow Lake) all supports SRIOV.

 

Background:

I am thinking about upgrading from 12700k to 265K as current motherboard can't support more ram.

If Arrow Lake is currently unsupported due to driver or kernel issue, where can I find the source so I can check progress myself?

Thanks in advance 

 

I had someone verify SRIOV to be working on an 14100.

 

But for the 265k afaik you'll need to wait for the XE driver with sriov function which is is still in development.

Hi all.

I've installed the plugin and passed through the VF's to a windows vm and all is well.
When I try to pass a separate VF to an ubuntu machine I get these errors from dmesg: 
[    1.764465] xe 0000:06:00.0: [drm] *ERROR* Hardware reported no preallocated GSM
[    1.764468] xe 0000:06:00.0: probe with driver xe failed with error -12

After googling I applied these parameters to my grub profile in the ubuntu vm: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash xe.force_probe=a782 i915.force_probe=!a782 mem=8G"

The VM details are:

• Ubuntu 24.04.2 LTS
• Kernel 6.11.0-19-generic

Any assistance that guys could provide would be greatly appreciated.
Thanks

on latest BETA 7.1 (Beta 1) plugin seems broken.

 

no virtual gpus can be created, stays at 0

 

if i set for example 1 or 2 , the site will "stuck" , if i refresh site, still at 0.

 

uninstall - reboot - reinstall - reboot , didnt fix the issue.

 

i5 14500

update needed?

Unraid 7.1.0-beta.1

 

It doesn't work. I tried adding echo "blacklist xe" >> /boot/config/modprobe.d/i915.conf but it didn't work.

 

dmesg | grep i915
               use xe.force_probe='4680' and i915.force_probe='!4680'
[   91.821086] i915: unknown parameter 'max_vfs' ignored
[   91.821572] i915 0000:00:02.0: [drm] Found ALDERLAKE_S (device ID 4680) display version 12.00 stepping C0
[   91.822526] i915 0000:00:02.0: [drm] VT-d active for gfx access
[   91.822531] i915 0000:00:02.0: vgaarb: deactivate vga console
[   91.822580] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[   91.823577] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   91.830751] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/adls_dmc_ver2_01.bin (v2.1)
[   91.858970] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 70.36.0
[   91.858976] i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
[   91.862107] i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
[   91.862837] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[   91.862839] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[   91.863221] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[   91.863739] mei_pxp 0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:00:02.0 (ops i915_pxp_tee_component_ops [i915])
[   91.863890] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[   91.863894] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[   91.865393] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0
[   91.886670] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[   91.926666] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[   91.946664] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[   93.903601] i915 0000:00:02.0: driver does not support SR-IOV configuration via sysfs

 

Edited March 19, 20251 yr by neunghaha28

A fix for it will be available soon. This *should* only affect 7.1.0-beta.1 (in case someone reads it in the future)

21 hours ago, Encore said:

on latest BETA 7.1 (Beta 1) plugin seems broken.

4 hours ago, neunghaha28 said:

Unraid 7.1.0-beta.1

The fix is out now, it would be best to fully remove the plugin, then install it again from the CA App and reboot, after that SR-IOV should work again.

 

The cause of this issue was actually a change in the Kernel which lead to uncompressed Kernel modules in Unraid 7.1.0-beta.1 which prevented the compressed module from loading properly.

1 hour ago, ich777 said:

The fix is out now, it would be best to fully remove the plugin, then install it again from the CA App and reboot, after that SR-IOV should work again.

 

The cause of this issue was actually a change in the Kernel and lead to uncompressed Kernel modules in Unraid 7.1.0-beta.1 which prevented the compressed module from loading properly.

 

Thx, uninstalled and reinstalled the plugin and it worked fine.

 

 

Mar 19 13:27:13 NAS kernel: x86/split lock detection: #AC: CPU 3/KVM/47448 took a split_lock trap at address: 0x7320c96d
Mar 19 13:27:35 NAS kernel: i915 0000:00:02.0: VF1 FLR
Mar 19 13:29:33 NAS autofan: Highest disk temp is 32C, adjusting fan speed from: 40 (15% @ 1170rpm) to: 55 (21% @ 1298rpm)
Mar 19 13:29:33 NAS autofan: Highest disk temp is 32C, adjusting fan speed from: 51 (20% @ 1170rpm) to: 57 (22% @ 1298rpm)
Mar 19 13:30:01 NAS docker: Success: Backup of RAM-Disk created.
Mar 19 13:32:39 NAS autofan: Highest disk temp is 33C, adjusting fan speed from: 55 (21% @ 1305rpm) to: 70 (27% @ 1464rpm)
Mar 19 13:32:39 NAS autofan: Highest disk temp is 33C, adjusting fan speed from: 57 (22% @ 1305rpm) to: 63 (24% @ 1464rpm)
Mar 19 13:34:44 NAS kernel: br0: port 3(vnet2) entered disabled state
Mar 19 13:34:44 NAS kernel: vnet2 (unregistering): left allmulticast mode
Mar 19 13:34:44 NAS kernel: vnet2 (unregistering): left promiscuous mode
Mar 19 13:34:44 NAS kernel: br0: port 3(vnet2) entered disabled state
Mar 19 13:34:45 NAS kernel: i915 0000:00:02.0: VF1 FLR
Mar 19 13:34:47 NAS kernel: vfio-pci 0000:00:02.1: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none
Mar 19 13:34:47 NAS kernel: xe 0000:00:02.1: Your graphics device 4680 is not officially supported
Mar 19 13:34:47 NAS kernel: by xe driver in this kernel version. To force Xe probe,
Mar 19 13:34:47 NAS kernel: use xe.force_probe='4680' and i915.force_probe='!4680'
Mar 19 13:34:47 NAS kernel: module parameters or CONFIG_DRM_XE_FORCE_PROBE='4680' and
Mar 19 13:34:47 NAS kernel: CONFIG_DRM_I915_FORCE_PROBE='!4680' configuration options.
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] Found ALDERLAKE_S (device ID 4680) display version 12.00 stepping C0
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: Running in SR-IOV VF mode
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] GT0: GUC: interface version 0.1.17.0
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] VT-d active for gfx access
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] Using Transparent Hugepages
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] GT0: GUC: interface version 0.1.17.0
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] GT0: GUC: interface version 0.1.17.0
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: GuC firmware PRELOADED version 0.0 submission:SR-IOV VF
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: HuC firmware PRELOADED
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] Protected Xe Path (PXP) protected content support initialized
Mar 19 13:34:47 NAS kernel: i915 0000:00:02.1: [drm] PMU not supported for this GPU.
Mar 19 13:34:47 NAS kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.1 on minor 1
Mar 19 13:34:47 NAS usb_manager: Info: rc.usb_manager  vm_action Windows 11 stopped end -
Mar 19 13:34:49 NAS kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=none:owns=io+mem
Mar 19 13:34:49 NAS kernel: i915 0000:00:02.2: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Mar 19 13:34:49 NAS kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=io+mem:owns=io+mem
Mar 19 13:34:50 NAS kernel: i915 0000:00:02.0: Disabled 2 VFs
Mar 19 13:34:50 NAS kernel: Console: switching to colour dummy device 80x25
Mar 19 13:34:51 NAS acpid: input device has been disconnected, fd 11
Mar 19 13:35:45 NAS autofan: Highest disk temp is 34C, adjusting fan speed from: 70 (27% @ 1513rpm) to: 85 (33% @ 1650rpm)
Mar 19 13:35:45 NAS autofan: Highest disk temp is 34C, adjusting fan speed from: 63 (24% @ 1513rpm) to: 69 (27% @ 1650rpm)
Mar 19 13:35:54 NAS kernel: ------------[ cut here ]------------
Mar 19 13:35:54 NAS kernel: pci 0000:00:02.0: [drm] pm_runtime_get_sync() failed: -13
Mar 19 13:35:54 NAS kernel: WARNING: CPU: 10 PID: 108561 at /usr/src/i915-sriov-dkms/drivers/gpu/drm/i915/intel_runtime_pm.c:171 __intel_runtime_pm_get.isra.0+0x62/0x80 [i915]
Mar 19 13:35:54 NAS kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap ipvlan xt_nat xt_tcpudp nf_conntrack_netlink veth xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype cfg80211 rfkill md_mod ntfs3 tcp_diag inet_diag i915(O) intel_gtt nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge 8021q garp mrp stp llc zfs(PO) xe intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_gpuvm sha256_ssse3 drm_exec sha1_ssse3 gpu_sched spl(O) drm_buddy aesni_intel drm_ttm_helper crypto_simd ttm cryptd i2c_algo_bit drm_suballoc_helper sr_mod drm_display_helper joydev cdrom input_leds mei_hdcp mei_pxp rapl drm_kms_helper intel_cstate wmi_bmof r8169 drm mpt3sas nvme i2c_i801 mei_me ahci realtek raid_class
Mar 19 13:35:54 NAS kernel: agpgart i2c_smbus intel_uncore libahci scsi_transport_sas led_class mei nvme_core vmd i2c_core fan thermal tpm_crb tpm_tis video tpm_tis_core tpm libaescfb ecdh_generic wmi backlight ecc acpi_tad acpi_pad button
Mar 19 13:35:54 NAS kernel: CPU: 10 UID: 99 PID: 108561 Comm: ffmpeg Tainted: P     U     O       6.12.19-Unraid #1
Mar 19 13:35:54 NAS kernel: Tainted: [P]=PROPRIETARY_MODULE, [U]=USER, [O]=OOT_MODULE
Mar 19 13:35:54 NAS kernel: Hardware name: ASUS System Product Name/PRIME B760M-A, BIOS 1661 06/25/2024
Mar 19 13:35:54 NAS kernel: RIP: 0010:__intel_runtime_pm_get.isra.0+0x62/0x80 [i915]
Mar 19 13:35:54 NAS kernel: Code: 5d 1a 00 01 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 b3 cc 59 e0 44 89 e1 4c 89 ea 48 c7 c7 45 63 58 a1 48 89 c6 e8 fe f8 e6 df <0f> 0b 40 0f b6 f5 48 89 df 5b 5d 41 5c 41 5d e9 ea fe ff ff 66 2e
Mar 19 13:35:54 NAS kernel: RSP: 0018:ffffc9000d5c7cf8 EFLAGS: 00010282
Mar 19 13:35:54 NAS kernel: RAX: 0000000000000000 RBX: ffff8881960320a0 RCX: 0000000000000027
Mar 19 13:35:54 NAS kernel: RDX: 0000000000000002 RSI: ffffffff8233aad5 RDI: 00000000ffffffff
Mar 19 13:35:54 NAS kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff82d96e50
Mar 19 13:35:54 NAS kernel: R10: 00003fffffffffff R11: 0000000000001458 R12: 00000000fffffff3
Mar 19 13:35:54 NAS kernel: R13: ffff888101d441a0 R14: ffff8881004faf80 R15: 0000000000000001
Mar 19 13:35:54 NAS kernel: FS:  0000000000000000(0000) GS:ffff88981f480000(0000) knlGS:0000000000000000
Mar 19 13:35:54 NAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 19 13:35:54 NAS kernel: CR2: 000015343fb612c8 CR3: 0000000005418006 CR4: 0000000000772ef0
Mar 19 13:35:54 NAS kernel: PKRU: 55555554
Mar 19 13:35:54 NAS kernel: Call Trace:
Mar 19 13:35:54 NAS kernel: <TASK>
Mar 19 13:35:54 NAS kernel: ? __warn+0x90/0x120
Mar 19 13:35:54 NAS kernel: ? report_bug+0xe2/0x160
Mar 19 13:35:54 NAS kernel: ? __intel_runtime_pm_get.isra.0+0x62/0x80 [i915]
Mar 19 13:35:54 NAS kernel: ? handle_bug+0x53/0x80
Mar 19 13:35:54 NAS kernel: ? exc_invalid_op+0x13/0x60
Mar 19 13:35:54 NAS kernel: ? asm_exc_invalid_op+0x16/0x20
Mar 19 13:35:54 NAS kernel: ? __intel_runtime_pm_get.isra.0+0x62/0x80 [i915]
Mar 19 13:35:54 NAS kernel: ? __intel_runtime_pm_get.isra.0+0x62/0x80 [i915]
Mar 19 13:35:54 NAS kernel: intel_runtime_pm_get+0xf/0x20 [i915]
Mar 19 13:35:54 NAS kernel: i915_driver_release+0x22/0x80 [i915]
Mar 19 13:35:54 NAS kernel: drm_dev_put+0x39/0x70 [drm]
Mar 19 13:35:54 NAS kernel: singleton_release+0x1c/0x30 [i915]
Mar 19 13:35:54 NAS kernel: __fput+0x106/0x1d0
Mar 19 13:35:54 NAS kernel: task_work_run+0x67/0x80
Mar 19 13:35:54 NAS kernel: do_exit+0x36c/0x8c0
Mar 19 13:35:54 NAS kernel: ? __pfx_futex_wake_mark+0x10/0x10
Mar 19 13:35:54 NAS kernel: do_group_exit+0x79/0x80
Mar 19 13:35:54 NAS kernel: get_signal+0x61a/0x660
Mar 19 13:35:54 NAS kernel: ? __seccomp_filter+0x83/0x380
Mar 19 13:35:54 NAS kernel: arch_do_signal_or_restart+0x2a/0x1f0
Mar 19 13:35:54 NAS kernel: ? do_futex+0xe6/0x170
Mar 19 13:35:54 NAS kernel: ? __do_sys_futex+0x11f/0x150
Mar 19 13:35:54 NAS kernel: ? syscall_trace_enter+0x61/0x130
Mar 19 13:35:54 NAS kernel: syscall_exit_to_user_mode+0x4f/0x80
Mar 19 13:35:54 NAS kernel: do_syscall_64+0x82/0xe0
Mar 19 13:35:54 NAS kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e
Mar 19 13:35:54 NAS kernel: RIP: 0033:0x15343c898d71
Mar 19 13:35:54 NAS kernel: Code: Unable to access opcode bytes at 0x15343c898d47.
Mar 19 13:35:54 NAS kernel: RSP: 002b:00001534327fa720 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
Mar 19 13:35:54 NAS kernel: RAX: fffffffffffffe00 RBX: 0000557bbf63b408 RCX: 000015343c898d71
Mar 19 13:35:54 NAS kernel: RDX: 0000000000000000 RSI: 0000000000000189 RDI: 0000557bbf63b434
Mar 19 13:35:54 NAS kernel: RBP: 00001534327fa760 R08: 0000000000000000 R09: 00000000ffffffff
Mar 19 13:35:54 NAS kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
Mar 19 13:35:54 NAS kernel: R13: 0000000000000000 R14: 0000557bbecb2eb8 R15: 0000557bbf63b434
Mar 19 13:35:54 NAS kernel: </TASK>
Mar 19 13:35:54 NAS kernel: ---[ end trace 0000000000000000 ]---

i5 14500 - crashs on windows 11 VM - need to reboot host system to get my igpu back / igpu disapears after some minutes or reboot/shutdown the VM 

 

tested a bit with chatgpt:

i915.enable_psr=0 i915.enable_rc6=0 i915.runtime_pm=0 doesnt work 

 

The new log you provided shows a similar warning related to the i915 driver, specifically the Intel GPU runtime power management function (pm_runtime_get_sync()) failing. The error code -13 indicates a permission issue, which might suggest the driver is encountering a power management issue or there's an issue with accessing the GPU's power states.

Here’s a breakdown of the log:

Warning:

pm_runtime_get_sync() failed: -13: This message indicates that the driver failed to sync the power management state for the GPU. The error code -13 usually indicates a permission issue (EACCESS), meaning that the function couldn't access the necessary resources or permissions to manage the GPU's power state.
Driver and Kernel Involved:

The log references the i915 driver, which is used for Intel graphics. This is the same driver mentioned in your earlier log.
It also mentions the intel_runtime_pm_get function and the i915_driver_release function, which are part of the GPU power management and driver release processes.
System Information:

The hardware appears to be an ASUS motherboard (PRIME B760M-A) with a BIOS version from June 2024.
It’s running Unraid OS (6.12.19-Unraid).
Additional Context:

The process ffmpeg seems to be running at the time of the error. If you are doing some video processing or utilizing the GPU with ffmpeg, this could be relevant, as ffmpeg may be interacting with the GPU through the driver.
Possible Solutions:
Here are a few things you could try to resolve or investigate the issue further:

Update i915 and Kernel:

Check if there are any updates for the i915 driver or the kernel. Sometimes, these power management issues are resolved in newer versions of the kernel or driver patches.
Check BIOS Settings:

Make sure that your BIOS settings related to power management and Intel graphics are properly configured. This includes ensuring that settings like Intel C-states or GPU power management are not causing conflicts.
Verify GPU Access Permissions:

Ensure that the process has the necessary permissions to access the GPU. This could involve checking system settings related to user permissions or ensuring that no conflicts are occurring with other processes or drivers.
Disable Runtime Power Management for i915:

As a test, you can try disabling runtime power management for the i915 driver. This can be done by adding the following kernel parameter:
ini
Kopieren
i915.enable_psr=0
or by blacklisting the intel_pstate driver, depending on your exact setup.
Test with Another GPU (if available):

If you have a separate GPU available, test with that to see if the issue is related specifically to the Intel integrated GPU.
Look for Conflicting Drivers or Modules:

Ensure no other conflicting drivers or modules are loaded that could interfere with the i915 driver. You can check this by reviewing your list of loaded modules and ensuring they aren't overlapping in functionality.

 

blacklisting xe driver doesnt work too.

Edited March 19, 20251 yr by Encore

I've read all comments but cannot find my specific usecase - so a question - maybe already answerded, sorry for that!

 

I have the plugin working. I have a workVM - that i want to use on the HDMI and Displayport output, so i have to choose 2.0, i have to vfs made - 2.1 and 2.2, thats working. I also have jellyfin, using transcoding. When i select 2.0 to output to the hdmi, will jellyfin still have transcoding, or does that only work on the 2.1 and 2.2 SRIOV?

 

Many thanks in advance! 

I have just upgraded to 7.1 beta1. The CPU is 14700T，GPU is UHD770. I can't use the i915 SRIOV plugin properly. Is it because the plugin is not compatible with 7.1?

12 minutes ago, yxlqqufo said:

I have just upgraded to 7.1 beta1. The CPU is 14700T，GPU is UHD770. I can't use the i915 SRIOV plugin properly. Is it because the plugin is not compatible with 7.1?

the latest version is compatible, so if you upgraded your plugin you should be fine if it was working before

with 7.1 it hangs on boot, it mentions the i915 and then nothing happens, had to restore an back-up

 

(12500t)

On 2/25/2025 at 12:10 AM, Orion676 said:

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

Do you "switch" / convert your Win VM from i440fx to Q35, or did you make a new Win VM with Q35? I would like to convert my VM from i440fx to Q35 if possible.

It has been some time, and I would like to ask if this plug-in can be used normally on the latest platforms?

Intel® Core™ Ultra Processor ( Arrow Lake)

Is it possible passthru a VF to a VM and have the 0000:00:02.0 available for containers?

I get the 0000:00:02.1 in the VM and installed Intel Drivers. But the VM crashes after some time.

Happy for feedback.

1 hour ago, frodr said:

I get the 0000:00:02.1 in the VM and installed Intel Drivers.

thats the way to go and the correct device, .1, 2, ...

1 hour ago, frodr said:

But the VM crashes after some time.

may leave some more Infos ... what VM ? Win ?

if so, how are you connecting to it ? if its RDP ... suffers from vram ... etc etc ...

4 hours ago, alturismo said:

thats the way to go and the correct device, .1, 2, ...

may leave some more Infos ... what VM ? Win ?

if so, how are you connecting to it ? if its RDP ... suffers from vram ... etc etc ...

Its Win11 VM´s,

i440fx-9.2

Connected with Microsoft Remote Desktop from Mac.

Any other infomation I need to add?

Also, I noticed that a QSV transcode (HandBrake) in this VM did fail. (Worked well in another VM (nvenc) on another server.

Another question, when running SR-IOV is the "/dev/dri/“ parameter in the plex/jellyfin template sufficient, or should a specific VF be applied?

Edited June 10, 20251 yr by frodr
More questions.

7 hours ago, frodr said:

i440fx-9.2

may consider in future using q35 ...

7 hours ago, frodr said:

Connected with Microsoft Remote Desktop

out of experience (from earlier gvt-g ...) RDP somehow likes to break stuff as its using more vram and the VM likes to crash, worst case Server even crashes ... so i switched on gvt / iov VM's to use parsec for remote, better (more fluid) experience and more stable then RDP, actually never had a crash since then ...

this likes to happen when the RDP client using higher resolution ...

on dedicated dGPU VM's RDP works fine, but also there streaming is more fluid ;) just as note.

7 hours ago, frodr said:

Also, I noticed that a QSV transcode (HandBrake) in this VM did fail. (Worked well in another VM (nvenc) on another server.

then its most likely not properly running anyway, working fine here, encoding, funmark (low fps of course), ...

then you know its setted up correctly and the vgpu is working too, may need a virtual display (vdd driver as sample)

but, upper emntioned streaming wont work prolly as its not setup correctly anyway in the current state.

7 hours ago, frodr said:

Another question, when running SR-IOV is the "/dev/dri/“ parameter in the plex/jellyfin template sufficient, or should a specific VF be applied?

yes, thats enough then, nothing special needed for dockers, the vgpu's are only for the VM's ...

Hi, I have the

• Unraid 7.1.4

• Intel® Core™ Ultra 7 265K

• 8086:7d67] 00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06) (not bound)

• I have the Intel CPU Top plugin, and confirmed on the driver page Xe Drivers are loaded.

• Removed multiple times

When I go to enable VFs, It tell me its supported. Total VFs Available = 0

Created VFs: blank

When I click the VF Numbers dropdown, it shows 0.

cat /boot/config/modproble.d/xe.confg =

• options xe force_probe=7d67

cat /boot/config/modproble.d/i915.confg =

• options i915 enable_guc=7

• options i915 force_probe=!7d67

• blacklist i915

---

I f I bind the VGA Adapter, the app lets me set stuff but still no luck. My understanding is I should leave it unbound.

Not sure if I'm missing something or just need to wait another few months.

Thanks for taking a look

Edited July 15, 2025Jul 15 by AndrewGG