From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 532BCA04CC; Mon, 21 Sep 2020 13:58:13 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CFAEE1D95B; Mon, 21 Sep 2020 13:58:12 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id 296881D94B for ; Mon, 21 Sep 2020 13:58:11 +0200 (CEST) IronPort-SDR: WRXuuXk5a5VxrKaFBT4LTodWXKZ/ddBv3Arcri49hSjxZGKHrywAE6ikVm93g2O43JUu9x4KEe cAphPIGfB3dQ== X-IronPort-AV: E=McAfee;i="6000,8403,9750"; a="139857292" X-IronPort-AV: E=Sophos;i="5.77,286,1596524400"; d="scan'208";a="139857292" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 04:58:08 -0700 IronPort-SDR: UaaoH8PeGHtqtipkr+Wccjx+tZ7Dh6+NXUPXG1gTEeVBLdHw2HHCF7Cuy1mZ8q9NCwGZ5c09T5 6nUiEmHqv5oQ== X-IronPort-AV: E=Sophos;i="5.77,286,1596524400"; d="scan'208";a="485413124" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.213.248.121]) ([10.213.248.121]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 04:58:07 -0700 To: Sarosh Arif Cc: Bruce Richardson , dev@dpdk.org References: <20200917091723.GD1568@bricha3-MOBL.ger.corp.intel.com> <9009b751-c6fa-7195-368b-ed7a1d2c91f5@intel.com> From: "Burakov, Anatoly" Message-ID: <462372ab-e656-4c32-98e2-4a30e834b763@intel.com> Date: Mon, 21 Sep 2020 12:58:05 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] unable to bind to vfio-pci X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 21-Sep-20 12:54 PM, Sarosh Arif wrote: > On Thu, Sep 17, 2020 at 2:35 PM Burakov, Anatoly > wrote: >> >> On 17-Sep-20 10:21 AM, Sarosh Arif wrote: >>> On Thu, Sep 17, 2020 at 2:17 PM Bruce Richardson >>> 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