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 18B2CA04BC for ; Fri, 9 Oct 2020 13:14:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id F354C1D412; Fri, 9 Oct 2020 13:14:34 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 6091F1D407 for ; Fri, 9 Oct 2020 13:14:32 +0200 (CEST) IronPort-SDR: mmlQFwTstbzpzzefPVlR9rJBUByVaNB0BHYsYZ0IqMhiv7CFtnLLjNxIKAj/oijpOgBfAQsLcv p4LqnDsYGIDQ== X-IronPort-AV: E=McAfee;i="6000,8403,9768"; a="145336395" X-IronPort-AV: E=Sophos;i="5.77,354,1596524400"; d="scan'208";a="145336395" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Oct 2020 04:14:29 -0700 IronPort-SDR: BleS2ycAZQisjCuUu9DaRKrUzHicixpTvYhn+x1f2kQkgDxCzYcfBgjkx2781dWUi55rsKA1dA Vy7NFl/vrQYw== X-IronPort-AV: E=Sophos;i="5.77,354,1596524400"; d="scan'208";a="462153832" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.252.18.7]) ([10.252.18.7]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Oct 2020 04:14:27 -0700 To: Brandon Lo Cc: ci@dpdk.org, "Chen, Zhaoyan" , "Tu, Lijuan" , "Xu, Qian Q" References: <2a8add68-adad-7780-83be-324898a154a5@intel.com> From: Ferruh Yigit Message-ID: <8c696743-5640-9ad9-aba4-916ca8858f64@intel.com> Date: Fri, 9 Oct 2020 12:14:24 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-ci] Intel VFIO-PCI Driver Error -22 X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" 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 wrote: >> >> Thanks, I was not aware that the system had Vt-d disabled. >> >> On Thu, Oct 8, 2020 at 1:46 PM Ferruh Yigit 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 > > >