DPDK CI discussions
 help / color / mirror / Atom feed
* [dpdk-ci] Intel VFIO-PCI Driver Error -22
@ 2020-10-08 16:51 Brandon Lo
  2020-10-08 17:46 ` Ferruh Yigit
  0 siblings, 1 reply; 6+ messages in thread
From: Brandon Lo @ 2020-10-08 16:51 UTC (permalink / raw)
  To: ci, Chen, Zhaoyan, Tu, Lijuan, Xu, Qian Q

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.

Thanks,
Brandon
-- 
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
  2020-10-08 16:51 [dpdk-ci] Intel VFIO-PCI Driver Error -22 Brandon Lo
@ 2020-10-08 17:46 ` Ferruh Yigit
  2020-10-08 18:19   ` Brandon Lo
  0 siblings, 1 reply; 6+ messages in thread
From: Ferruh Yigit @ 2020-10-08 17:46 UTC (permalink / raw)
  To: Brandon Lo, ci, Chen, Zhaoyan, Tu, Lijuan, Xu, Qian Q

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?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
  2020-10-08 17:46 ` Ferruh Yigit
@ 2020-10-08 18:19   ` Brandon Lo
  2020-10-08 18:30     ` Brandon Lo
  0 siblings, 1 reply; 6+ messages in thread
From: Brandon Lo @ 2020-10-08 18:19 UTC (permalink / raw)
  To: Ferruh Yigit; +Cc: ci, Chen, Zhaoyan, Tu, Lijuan, Xu, Qian Q

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@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@iol.unh.edu

www.iol.unh.edu

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
  2020-10-08 18:19   ` Brandon Lo
@ 2020-10-08 18:30     ` Brandon Lo
  2020-10-09  9:58       ` Juraj Linkeš
  2020-10-09 11:14       ` Ferruh Yigit
  0 siblings, 2 replies; 6+ messages in thread
From: Brandon Lo @ 2020-10-08 18:30 UTC (permalink / raw)
  To: Ferruh Yigit; +Cc: ci, Chen, Zhaoyan, Tu, Lijuan, Xu, Qian Q

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?

Thanks,
Brandon

On Thu, Oct 8, 2020 at 2:19 PM Brandon Lo <blo@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@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@iol.unh.edu
>
> www.iol.unh.edu



-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
  2020-10-08 18:30     ` Brandon Lo
@ 2020-10-09  9:58       ` Juraj Linkeš
  2020-10-09 11:14       ` Ferruh Yigit
  1 sibling, 0 replies; 6+ messages in thread
From: Juraj Linkeš @ 2020-10-09  9:58 UTC (permalink / raw)
  To: Brandon Lo, Ferruh Yigit; +Cc: ci, Chen, Zhaoyan, Tu, Lijuan, Xu, Qian Q

It's possible that vfio-pci is not loaded, /sys/bus/pci/drivers//unbind is missing vfio-pci in the path.

Try to modprobe vfio-pci and see whether it shows under /sys/bus/pci/drivers/.

If this is the case, then you may want to add vfio-pci to /etc/modules so that it gets loaded automatically on boot.

Juraj

> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of Brandon Lo
> Sent: Thursday, October 8, 2020 8:30 PM
> To: Ferruh Yigit <ferruh.yigit@intel.com>
> Cc: ci@dpdk.org; Chen, Zhaoyan <zhaoyan.chen@intel.com>; Tu, Lijuan
> <lijuan.tu@intel.com>; Xu, Qian Q <qian.q.xu@intel.com>
> Subject: Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
> 
> 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?
> 
> Thanks,
> Brandon
> 
> On Thu, Oct 8, 2020 at 2:19 PM Brandon Lo <blo@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@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@iol.unh.edu
> >
> > www.iol.unh.edu
> 
> 
> 
> --
> 
> Brandon Lo
> 
> UNH InterOperability Laboratory
> 
> 21 Madbury Rd, Suite 100, Durham, NH 03824
> 
> blo@iol.unh.edu
> 
> www.iol.unh.edu


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22
  2020-10-08 18:30     ` Brandon Lo
  2020-10-09  9:58       ` Juraj Linkeš
@ 2020-10-09 11:14       ` Ferruh Yigit
  1 sibling, 0 replies; 6+ messages in thread
From: Ferruh Yigit @ 2020-10-09 11:14 UTC (permalink / raw)
  To: Brandon Lo; +Cc: ci, Chen, Zhaoyan, Tu, Lijuan, Xu, Qian Q

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@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@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@iol.unh.edu
>>
>> www.iol.unh.edu
> 
> 
> 


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-10-09 11:14 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-08 16:51 [dpdk-ci] Intel VFIO-PCI Driver Error -22 Brandon Lo
2020-10-08 17:46 ` Ferruh Yigit
2020-10-08 18:19   ` Brandon Lo
2020-10-08 18:30     ` Brandon Lo
2020-10-09  9:58       ` Juraj Linkeš
2020-10-09 11:14       ` Ferruh Yigit

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).