[dpdk-ci] Intel VFIO-PCI Driver Error -22

[Ferruh Yigit]

On 10/8/2020 7:30 PM, Brandon Lo wrote:
> I may have sent that thanks email too early.
> 
> Vt-d is enabled now for both machines, but the same error -22 is still
> occurring in dmesg.
> 
> `/sys/kernel/iommu_groups/` is empty.
> Perhaps the kernel parameters are not being set properly?
> 

if iommu enabled '/sys/kernel/iommu_groups/' should have folders in.

What did you enable in the bios, it mostly doesn't come with name 'Vt-d' so may 
be hard to find it?

The kernel parameters "intel_iommu=on iommu=pt" looks good.

> Thanks,
> Brandon
> 
> On Thu, Oct 8, 2020 at 2:19 PM Brandon Lo <blo at iol.unh.edu> wrote:
>>
>> Thanks, I was not aware that the system had Vt-d disabled.
>>
>> On Thu, Oct 8, 2020 at 1:46 PM Ferruh Yigit <ferruh.yigit at intel.com> wrote:
>>>
>>> On 10/8/2020 5:51 PM, Brandon Lo wrote:
>>>> Hi everyone,
>>>>
>>>> I am having issues trying to bind both Intel Niantic and Fortville
>>>> NICs over to VFIO-PCI.
>>>> The machines are running Ubuntu 18.04 with kernel 4.15.0-55.
>>>> The dpdk-devbind.py tool outputs "Cannot bind to driver vfio-pci" and
>>>> "Cannot open /sys/bus/pci/drivers//unbind".
>>>>
>>>> The dmesg output contains "vfio-pci: probe of [PCI Address] failed
>>>> with error -22" whenever I try to bind it.
>>>> Both machines have "intel_iommu=on iommu=pt" in their kernel parameters.
>>>>
>>>
>>> Is 'Vt-d' enabled in the bios?
>>>
>>> What do you see under '/sys/kernel/iommu_groups/' folder?
>>
>>
>>
>> --
>>
>> Brandon Lo
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> blo at iol.unh.edu
>>
>> www.iol.unh.edu
> 
> 
>