From: Stephen Hemminger <stephen@networkplumber.org>
To: sysman@scaled.cloud
Cc: users@dpdk.org
Subject: Re: How to resolve "Not all devices in IOMMU group bound to VFIO or unbound" ?
Date: Wed, 10 Aug 2022 06:55:25 -0700 [thread overview]
Message-ID: <20220810065525.204e1901@hermes.local> (raw)
In-Reply-To: <e64724fd9af59c9c4967284e8570f0eb@scaled.cloud>
On Wed, 10 Aug 2022 16:52:39 +0300
sysman@scaled.cloud wrote:
> Hello!
>
> I have built and deployed latest DPDK from the git, so:
>
> dpdk-devbind.py -s
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:02:04.0 '82545EM Gigabit Ethernet Controller (Copper) 100f'
> drv=vfio-pci unused=e1000
> 0000:02:05.0 '82545EM Gigabit Ethernet Controller (Copper) 100f'
> drv=vfio-pci unused=e1000
> 0000:02:06.0 '82545EM Gigabit Ethernet Controller (Copper) 100f'
> drv=vfio-pci unused=e1000
> 0000:02:07.0 '82545EM Gigabit Ethernet Controller (Copper) 100f'
> drv=vfio-pci unused=e1000
>
> Network devices using kernel driver
> ===================================
> 0000:02:01.0 '82545EM Gigabit Ethernet Controller (Copper) 100f' if=eth0
> drv=e1000 unused=vfio-pci *Active*
>
>
>
> ./ipv4_multicast
> ...
> EAL: 0000:02:04.0 VFIO group is not viable! Not all devices in IOMMU
> group bound to VFIO or unbound
> EAL: Requested device 0000:02:04.0 cannot be used
> EAL: 0000:02:05.0 VFIO group is not viable! Not all devices in IOMMU
> group bound to VFIO or unbound
> EAL: Requested device 0000:02:05.0 cannot be used
> EAL: 0000:02:06.0 VFIO group is not viable! Not all devices in IOMMU
> group bound to VFIO or unbound
> EAL: Requested device 0000:02:06.0 cannot be used
> EAL: 0000:02:07.0 VFIO group is not viable! Not all devices in IOMMU
> group bound to VFIO or unbound
> EAL: Requested device 0000:02:07.0 cannot be used
> ...
>
>
> root@devuan4-sysman:~# readlink
> "/sys/bus/pci/devices/0000:02:04.0/iommu_group"
> ../../../../kernel/iommu_groups/5
> root@devuan4-sysman:~# readlink
> "/sys/bus/pci/devices/0000:02:05.0/iommu_group"
> ../../../../kernel/iommu_groups/5
> root@devuan4-sysman:~# readlink
> "/sys/bus/pci/devices/0000:02:06.0/iommu_group"
> ../../../../kernel/iommu_groups/5
> root@devuan4-sysman:~# readlink
> "/sys/bus/pci/devices/0000:02:07.0/iommu_group"
> ../../../../kernel/iommu_groups/5
>
>
>
> Can someone, please, help me resolve this problem?
Can't really be fixed in software, the IOMMU groups come from the hardware.
The best workaround if possible is to use a different NIC for eth0.
next prev parent reply other threads:[~2022-08-10 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99e01fff837b85c1126ef0a235078fc3@scaled.cloud>
2022-08-10 13:52 ` sysman
2022-08-10 13:55 ` Stephen Hemminger [this message]
2022-08-10 14:11 ` sysman
2022-08-10 14:19 ` Stephen Hemminger
2022-08-11 9:00 ` Error: bind failed for 0000:02:04.0 - Cannot bind to driver uio_pci_generic: [Errno 19] No such device sysman
2022-08-11 14:56 ` Stephen Hemminger
2022-08-25 10:50 ` DPD-22.07 bind error=-19 sysman
2022-09-10 8:28 ` IP/UDP packet reordering sysman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220810065525.204e1901@hermes.local \
--to=stephen@networkplumber.org \
--cc=sysman@scaled.cloud \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).