#SRIOV
wow. sriov
May 21, 2026 at 9:47 PM
Pas de live CuistOps ce soir 🌴🍹
Mais on se retrouve semaine prochaine pour un POC de SRIOV sur mon MS-01 🚀
June 16, 2025 at 8:11 AM
QEMUにigbのエミュレーション入ってるの知らなかった。SR-IOVがハードウェア無しで使えるらしい。これは地味に嬉しい。性能的なメリットは一切ないけど、CIとかでSRIOVテストするのが劇的に楽になる。

www.qemu.org/docs/master/...
igb — QEMU documentation
www.qemu.org
June 25, 2026 at 4:51 PM
This is where I live right now at work (bodging sriov support into an existing driver), can confirm
June 26, 2026 at 1:51 AM
I had major issues going the other way. Proxmox on kernel 6.8+ had some real issues with nvidia vGPU and SRIOV, that I solved by bypassing how proxmox handles it and allocating the vdevs myself.
But Server 2025 VMs don’t want to boot in KVM if cpu type is “host” with nested virtualization on
December 5, 2024 at 5:36 AM
I spent the last day trying to get SRIOV pass through working on the unsupported Tiger Lake. I kind of got to to work but it just crashes after like a minute. So basically, I wasted my day.
September 13, 2026 at 1:13 AM
Continuing on, it looks like when SR-IOV is removed I'm getting much better performance, although I will need to continue tuning this more to get where I want. It's unfortunate that #pfsense #SRIOV still seems completely broken - this has been reported for a very long time.
November 16, 2024 at 6:26 PM
It's pretty nice to see @pfsense running as a Kubernetes-based #KVM #virtualmachine with @kubevirt/@openshift. Even better with #Intel710 25G #SRIOV-based, isolated interfaces 🥳

@TomLawrenceTech This is what I've been wanting to show you for a little while now...👍
November 16, 2024 at 5:39 PM
Oh, and if #pfSense wasn't enough...I also have #Fortigate #VM running on #OpenShift as well (for 25G #SRIOV #Intel interfaces). Best part is they do bootstrap configuration and auto-licensing! What can I say...#openshiftvirtualization...just works! 😇
November 16, 2024 at 5:24 PM
There’s some nice new features coming to Qubes r4.3. Iirc better gpu acceleration support is on the roadmap. One that wouldn’t rely on sriov. Not sure if that will end up landing, but I’m also not sure when a rc will be cut.
July 15, 2025 at 1:17 PM
Panther Lake is the first generation that’s getting sriov support on mainline. Will be interesting to see if the linux-intel-lts branch is still kept up to date.
July 15, 2025 at 1:14 PM
I setup a GitHub repo that builds the intel-linux-lts kernel for qubes. It enables sriov for 11th gen-ultra 1, allowing gpu acceleration in vms. Add max_vfs=7 (or less) to the kernel command line to use it. Ultra also needs i915.force_probe=7d55 in both the host and vm. Vm also needs same kernel.
GitHub - burnskp/qubes-linux-kernel-intel: Qubes component: linux-kernel-intel
Qubes component: linux-kernel-intel. Contribute to burnskp/qubes-linux-kernel-intel development by creating an account on GitHub.
github.com
July 15, 2025 at 1:12 PM
Ordered a i7-1360p framework mainboard. Should be the latest cpu series that supports qubes r4.2 and sriov.

I really like framework, except for the heat they output. I tend to use my laptop on the couch and most laptops get too hot on the bottom for me. I usually put it on a hard mousepad.
July 9, 2025 at 3:28 PM
cpa_sample code get err could not start sal for user space
OS: Ubuntu 22.04 Kernel: Linux 5.15.0-140-generic x86_64 Firmware: Intel QAT 8970 HW Driver:  Lastest HW 1.* for Linux ,which is QAT.L.4.28.0-00004.tar.gz Compile cmd: ./configure --enable-icp-debug --enable-icp-log-syslog --enable-icp-sriov=host --enable-icp-qat-dbg Other info: intel_iommu=on has been added into grub configuration and IOMMU and SRIOV has been enabled  from the output of dmesg ,shown as below: [ 1.152230] Kernel command line: BOOT_IMAGE=/vmlinuz-5.15.0-140-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro intel_iommu=on [ 1.152287] DMAR: IOMMU enabled [ 2.353764] DMAR-IR: IOAPIC id 8 under DRHD base 0x9b7fc000 IOMMU 9 [ 4.338312] iommu: Default domain type: Translated [ 4.338312] iommu: DMA domain TLB invalidation policy: lazy mode VF has been created as : root@qat:~# lspci -d 8086:37c9 cc:01.0 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.1 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.2 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.3 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.4 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.5 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.6 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:01.7 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.0 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.1 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.2 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.3 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.4 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.5 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.6 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) cc:02.7 Co-processor: Intel Corporation C62x Chipset QuickAssist Technology Virtual Function (rev 04) Tests failed when running cpa_sample_code even add root as groupmember of "qat": root@qat:~# id root uid=0(root) gid=0(root) groups=0(root),1001(qat) root@qat:~# cpa_sample_code signOfLife=1 Latency computation Disabled qaeOpenFd:162 Memory file handle is not initialized. Initializing it now qaeMemInit started /QAT/quickassist/lookaside/access_layer/src/sample_code/performance/cpa_sample_code_main.c, main():506 Could not start sal for user space
community.intel.com
May 30, 2025 at 9:14 AM
LACP with SRIOV VFs inside a container is not working properly.
Hello, We are using following SRIOV NICs in our platforms. [root@appliance-1:Active] ~ # lspci -d 8086:1893 ec:00.4 Ethernet controller: Intel Corporation Ethernet Connection E822-C/X557-AT 10GBASE-T (rev 11) ec:00.5 Ethernet controller: Intel Corporation Ethernet Connection E822-C/X557-AT 10GBASE-T (rev 11) ec:00.6 Ethernet controller: Intel Corporation Ethernet Connection E822-C/X557-AT 10GBASE-T (rev 11) ec:00.7 Ethernet controller: Intel Corporation Ethernet Connection E822-C/X557-AT 10GBASE-T (rev 11) [root@appliance-1:Active] ~ # lspci -d 8086:1892 ec:00.0 Ethernet controller: Intel Corporation Ethernet Controller E822-C for SFP (rev 11) ec:00.1 Ethernet controller: Intel Corporation Ethernet Controller E822-C for SFP (rev 11) ec:00.2 Ethernet controller: Intel Corporation Ethernet Controller E822-C for SFP (rev 11) ec:00.3 Ethernet controller: Intel Corporation Ethernet Controller E822-C for SFP (rev 11) The nics are binded to iavf drivers. please find the driver details. [root@appliance-1:Active] ~ # modinfo iavf filename: /lib/modules/3.10.0-1160.71.1.F5.1.1.1.el7_8.x86_64/updates/drivers/net/ethernet/intel/iavf/iavf.ko version: 4.3.19 license: GPL description: Intel(R) Ethernet Adaptive Virtual Function Driver author: Intel Corporation, <linux.nics@intel.com> alias: i40evf retpoline: Y rhelversion: 7.9 srcversion: 58C0C08BF00AE634467AA8F alias: pci:v00008086d00001889sv*sd*bc*sc*i* alias: pci:v00008086d000037CDsv*sd*bc*sc*i* alias: pci:v00008086d00001571sv*sd*bc*sc*i* alias: pci:v00008086d0000154Csv*sd*bc*sc*i* depends: ptp,auxiliary vermagic: 3.10.0-1160.71.1.F5.1.1.1.el7_8.x86_64 SMP mod_unload modversions Scenario: On the platform/host, We have created a LACP LAG on the PFs. Creating a container allocating a vf from each PF using sriov CNI and creating the LACP using the  bond CNI. We see that interfaces and Bond is created successfully inside the container. We have followed this doc to configure LACP inside the container: <https://www.intel.com/content/www/us/en/developer/articles/technical/bond-cni.html> Issue: We have observed that LACP is not formed properly with VFs inside the container. The traffic doesn't passthrough from the container. Please let us know if you need any more details on the config and setup.
community.intel.com
September 18, 2024 at 7:43 AM
2014 SHRAORM SRIOV - $14182
June 7, 2025 at 6:59 PM
🚨 EUVD-2025-26103
📊 n/a
🏢 Linux

📝 In the Linux kernel, the following vulnerability has been resolved:

benet: fix BUG when creating VFs

benet crashes as soon as SRIOV VFs are created:

kernel...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-26103

#cybersecurity #infosec #cve #euvd
January 8, 2026 at 10:33 PM
🚨 EUVD-2023-60489
📊 n/a
🏢 Linux

📝 In the Linux kernel, the following vulnerability has been resolved:

powerpc/powernv/sriov: perform null check on iov before dereferencing iov

Currently point...

🔗 https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-60489

#cybersecurity #infosec #cve #euvd
December 30, 2025 at 2:50 PM