How to resolve "Not all devices in IOMMU group bound to VFIO or unbound" ?

sysman at scaled.cloud sysman at scaled.cloud
Wed Aug 10 16:11:04 CEST 2022


Hello!

    "The best workaround if possible is to use a different NIC for eth0."

  Can I ask u, please, explain with more words what I'm need to do ?
  Thanks!



Stephen Hemminger писал 2022-08-10 16:55:
> On Wed, 10 Aug 2022 16:52:39 +0300
> sysman at 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 at devuan4-sysman:~# readlink
>> "/sys/bus/pci/devices/0000:02:04.0/iommu_group"
>> ../../../../kernel/iommu_groups/5
>> root at devuan4-sysman:~# readlink
>> "/sys/bus/pci/devices/0000:02:05.0/iommu_group"
>> ../../../../kernel/iommu_groups/5
>> root at devuan4-sysman:~# readlink
>> "/sys/bus/pci/devices/0000:02:06.0/iommu_group"
>> ../../../../kernel/iommu_groups/5
>> root at 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.


More information about the users mailing list