DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] unable to bind to vfio-pci
Date: Mon, 21 Sep 2020 12:58:05 +0100
Message-ID: <462372ab-e656-4c32-98e2-4a30e834b763@intel.com> (raw)
In-Reply-To: <CABoZmYP5NRSbXBx8R=k9JKxf9LnnPHv1sXxbGjAh3Z5G-qixWQ@mail.gmail.com>

On 21-Sep-20 12:54 PM, Sarosh Arif wrote:
> On Thu, Sep 17, 2020 at 2:35 PM Burakov, Anatoly
> <anatoly.burakov@intel.com> wrote:
>>
>> On 17-Sep-20 10:21 AM, Sarosh Arif wrote:
>>> On Thu, Sep 17, 2020 at 2:17 PM Bruce Richardson
>>> <bruce.richardson@intel.com> wrote:
>>>>
>>>> On Thu, Sep 17, 2020 at 11:52:58AM +0500, Sarosh Arif wrote:
>>>>> I have been trying to bind to vfio-pci using usertools/dpdk-devbind.py
>>>>> but am unable to do so. The reason behind this is that I am unable to
>>>>> write in /sys/bus/pci/drivers/vfio-pci/bind. Upon searching solutions
>>>>> I tried a couple of things such as setting iommu=pt and intel_iommu=on
>>>>> and ensured vt-d is enabled.
>>>>> Along with this I have made sure that the vfio-pci module is correctly
>>>>> loaded. I have also tried
>>>>>
>>>>> chmod 666 /sys/bus/pci/drivers/vfio-pci/bind
>>>>>
>>>>> So that I have permissions to write in this file.
>>>>>
>>>>> The error I get when I use usertools/dpdk-devbind.py to bind is this:
>>>>> Error: bind failed for 0000:b7:00.1 - Cannot bind to driver vfio-pci
>>>>>
>>>>> The details of 0000:b7:00.1 are as follows:
>>>>> Ethernet Connection X722 for 10GBASE-T 37d2' if=eno6 drv=i40e
>>>>>
>>>>> I have also unbinded The pci bridge to which 0000:b7:00.1 was connected.
>>>>>
>>>>> What more can be done to resolve this?
>>>>>
>>>> Since you describe changing permissions on the "bind" file, are you trying
>>>> to run dpdk-devbind.py as a non-root user? Does it work as root?
>>> I am running it as a root user. It does not work as a root user.
>>>
>>
>> Does "dmesg | tail" say anything of interest?
> This is the output of dmesg | tail:
> [136286.136271] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Down
> [221230.023654] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Up 10 Gbps,
> Flow Control: RX/TX
> [221230.024134] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Down
> [249273.956525] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Up 10 Gbps,
> Flow Control: RX/TX
> [249273.957003] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Down
> [314864.386303] EXT4-fs (sda1): mounting ext3 file system using the
> ext4 subsystem
> [314867.734973] EXT4-fs (sda1): mounted filesystem with ordered data
> mode. Opts: (null)
> [332584.888223] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Up 10 Gbps,
> Flow Control: RX/TX
> [332584.888700] ixgbe 0000:65:00.0 enp101s0f0: NIC Link is Down
> [358429.954026] VFIO - User Level meta-driver version: 0.3

So, nothing useful :)

To me, it starts to sound more and more like some kind of security 
measure. Either it's something like AppArmor/SELinux preventing you from 
binding the drivers, or maybe it's something like Secure Boot, or some 
other security-related feature. A "permission denied" error is usually 
indicative of such things.

I'm not really an expert on this so i can't tell you off the top of my 
head what to check, but my first stop would have been either Secure 
Boot-related settings, or SELinux/AppArmor logs.

>>
>> --
>> Thanks,
>> Anatoly


-- 
Thanks,
Anatoly

  reply	other threads:[~2020-09-21 11:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  6:52 Sarosh Arif
2020-09-17  7:31 ` Dybkowski, AdamX
2020-09-17  8:39   ` Sarosh Arif
2020-09-17  9:17 ` Bruce Richardson
2020-09-17  9:21   ` Sarosh Arif
2020-09-17  9:35     ` Burakov, Anatoly
2020-09-21 11:54       ` Sarosh Arif
2020-09-21 11:58         ` Burakov, Anatoly [this message]
2020-09-17 10:22     ` Bruce Richardson
2020-09-17 11:49       ` Burakov, Anatoly
2020-09-21 11:10         ` Sarosh Arif
2020-09-21 11:36           ` Burakov, Anatoly

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=462372ab-e656-4c32-98e2-4a30e834b763@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=sarosh.arif@emumba.com \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git