<html class="apple-mail-supports-explicit-dark-mode"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"> <div dir="ltr"><blockquote type="cite">On 18 May 2026, at 14:32, Christoph <cm@appliedprivacy.net> wrote: </blockquote></div><blockquote type="cite"><div dir="ltr">Hi, we are trying to setup a test environment for grout and run into the following error when starting it: + interface add port e1g1 devargs 0000:04:00.0 rxqs 2 EAL: Driver cannot attach the device (0000:04:00.0) EAL: Failed to attach device on primary process error: command failed: Operation not supported (EOPNOTSUPP) grout.service: Control process exited, code=exited, status=1/FAILURE Is it possible to use grout with Intel I226-V NICs? We were able to use that NIC with VPP/DPDK. According to the DPDK documentation these NICs should be supported: https://core.dpdk.org/supported/nics/intel/ We also get the same error using the RTL8125: https://core.dpdk.org/supported/nics/realtek/ We _are_ able to start grout when using the Intel X710 NICs only on the same host while excluding the I226-V and Realtek NICs from the grout.init configuration. </div></blockquote><blockquote type="cite"><div dir="ltr">We see the exact same error (EOPNOTSUPP) on Fedora 44 using an Intel I218-LM on a different host. </div></blockquote><div> </div><div>Hi Christoph,</div><div> </div><div>This is expected, as only a few selected drivers are included in grout. </div><div> </div><div> <a href="https://github.com/DPDK/grout/blob/0ab251be5d05a239378bf69698ff6601761e0f76/meson.build#L75">https://github.com/DPDK/grout/blob/0ab251be5d05a239378bf69698ff6601761e0f76/meson.build#L75</a></div><div> </div><div>'enable_drivers=net/virtio,net/vhost,net/i40e,net/ice,net/iavf,net/ixgbe,net/null,net/tap,common/mlx5,net/mlx5,bus/auxiliary,net/vmxnet3',</div><div> </div><div>You could either rebuild grout for a quick test or create an issue / PR to include theses drivers.</div><div> </div><div>If you create a PR, I’ll merge it right away, so you’ll be able to use the edge RPM / container. </div><div>I don’t have a testbed for these NICs though: while I could add these drivers, I prefer to have someone to verify that they work :-)</div><div> </div><div>HTH,</div><div>Christophe </div><div> </div> <blockquote type="cite"><div dir="ltr">lspci: ------ ... 04:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller I226-V [8086:125c] (rev 04) ... dpdk-devbind.py -s ------------------- Network devices using DPDK-compatible driver 0000:03:00.0 'RTL8125 2.5GbE Controller 8125' drv=vfio-pci unused=r8169 0000:04:00.0 'Ethernet Controller I226-V 125c' drv=vfio-pci unused=igc 0000:05:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci unused=i40e 0000:05:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=vfio-pci unused=i40e grout.init: -------------- # Datapath CPU affinity affinity cpus set control 0,1 datapath 2,22,4,24 # Physical ports creation interface add port e1g1 devargs 0000:04:00.0 rxqs 2 # Interface addresses address add 10.0.3.25/24 iface e1g1 used versions: -------------- debian 13 linux: 6.12.88+deb13-amd64 dpdk 24.11.4-0+deb13u1 grout 0.15.0+72-g62e9b088 I226-V firmware-version: 2017:888d we used the edge deb package: https://github.com/DPDK/grout/releases/download/edge/grout_amd64.deb from 2026-05-05 sha256:5daa7b1f3f2871f1ceba02f6f4cce5d11766c3f2df95996e17bf87e87a38970e and also get the same error using v0.15.0: https://github.com/DPDK/grout/releases/download/v0.15.0/grout_amd64.deb Although we mentioned multiple NICs we would like to proceed debugging with the Intel I226-V NIC. best regards, Christoph more verbose (-vvvv) grout output for the error using I226-V: ------------------------------------------------ EAL: Trying to obtain current memory policy. EAL: Setting policy MPOL_PREFERRED for socket 0 EAL: alloc_seg(): mmap() failed: Cannot allocate memory EAL: Ask a virtual area of 0x40000000 bytes EAL: Virtual area found at 0x140000000 (size = 0x40000000) EAL: attempted to allocate 1 segments, but only 0 were allocated EAL: Restoring previous memory policy: 4 EAL: Trying to obtain current memory policy. EAL: Setting policy MPOL_PREFERRED for socket 0 EAL: Restoring previous memory policy: 4 EAL: request: mp_malloc_sync EAL: No shared files mode enabled, IPC is disabled EAL: Heap on socket 0 was expanded by 4MB EAL: Trying to obtain current memory policy. EAL: Setting policy MPOL_PREFERRED for socket 0 EAL: alloc_seg(): mmap() failed: Cannot allocate memory EAL: Ask a virtual area of 0x40000000 bytes EAL: Virtual area found at 0x140000000 (size = 0x40000000) EAL: attempted to allocate 1 segments, but only 0 were allocated EAL: Restoring previous memory policy: 4 EAL: Trying to obtain current memory policy. EAL: Setting policy MPOL_PREFERRED for socket 0 EAL: Restoring previous memory policy: 4 EAL: request: mp_malloc_sync EAL: No shared files mode enabled, IPC is disabled EAL: Heap on socket 0 was expanded by 26MB EAL: Trying to obtain current memory policy. EAL: Setting policy MPOL_PREFERRED for socket 0 EAL: Restoring previous memory policy: 4 EAL: request: mp_malloc_sync EAL: No shared files mode enabled, IPC is disabled EAL: Heap on socket 0 was expanded by 130MB EAL: Trying to obtain current memory policy. EAL: Setting policy MPOL_PREFERRED for socket 0 EAL: Restoring previous memory policy: 4 EAL: request: mp_malloc_sync EAL: No shared files mode enabled, IPC is disabled EAL: Heap on socket 0 was expanded by 514MB IFACE: iface_event: iface event [0xacdc1001] ADD triggered for iface main. IFACE: iface_event: iface event [0xacdc1002] POST_ADD triggered for iface main. error: command failed: Operation not supported (EOPNOTSUPP) IFACE: iface_event: iface event [0xacdc1006] STATUS_UP triggered for iface main. EAL: Driver cannot attach the device (0000:04:00.0) EAL: Failed to attach device on primary process API: read_cb: pid=7479 id=3 req_type=0xacdc0001 (GR_IFACE_ADD) req_len=466 status=95 (Operation not supported) resp_len=0 API: disconnect_client: client pid=7479 disconnected grout.service: Control process exited, code=exited, status=1/FAILURE MAIN: signal_cb: received signal SIGTERM </div></blockquote></body></html>