From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 4EE345A57 for ; Fri, 29 May 2015 07:34:58 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 28 May 2015 22:34:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,514,1427785200"; d="scan'208";a="733524622" Received: from pgsmsx104.gar.corp.intel.com ([10.221.44.91]) by fmsmga002.fm.intel.com with ESMTP; 28 May 2015 22:34:56 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by PGSMSX104.gar.corp.intel.com (10.221.44.91) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 29 May 2015 13:34:55 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.109]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.94]) with mapi id 14.03.0224.002; Fri, 29 May 2015 13:34:54 +0800 From: "Ouyang, Changchun" To: "Dey, Souvik" , "dev@dpdk.org" Thread-Topic: Unable to bind Virtio_pci in DPDK1.7 Thread-Index: AdCZzAPCwh7zFxw4RNm5B3/INRXs/QABIFbw Date: Fri, 29 May 2015 05:34:53 +0000 Message-ID: References: In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 05:34:58 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Dey, Souvik > Sent: Friday, May 29, 2015 1:22 PM > To: dev@dpdk.org > Subject: [dpdk-dev] Unable to bind Virtio_pci in DPDK1.7 >=20 > Hi All, > I am currently facing a weird issue where I am not able t= o bind the > virtio_pci device to igb_uio in DPDK1.7 on QEMU/KVM. I can see there are > two fold issues. > 1.The pci_unbind.py script where the virt_path is removed from 1.6 to 1.7 > version due to which the initial status is not able to show any interface= name. >=20 > Network devices using DPDK-compatible driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >=20 > Network devices using kernel driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:00:03.0 'Virtio network device' if=3D drv=3Dvirtio-pci > unused=3Dvirtio_pci,igb_uio > 0000:00:04.0 'Virtio network device' if=3D drv=3Dvirtio-pci > unused=3Dvirtio_pci,igb_uio > 0000:00:05.0 'Virtio network device' if=3D drv=3Dvirtio-pci > unused=3Dvirtio_pci,igb_uio > 0000:00:06.0 'Virtio network device' if=3D drv=3Dvirtio-pci > unused=3Dvirtio_pci,igb_uio >=20 > Other network devices > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >=20 >=20 > 2. After correcting the above issue , I am stuck where the interface is f= ailing > to bind to igb_uio. I tried to bind the interface manually to igb_uio bu= t I am > getting the following error >=20 > lspci -k > 00:05.0 Ethernet controller: Red Hat, Inc Virtio network device > Subsystem: Red Hat, Inc Device 0001 > Kernel modules: virtio_pci >=20 > echo 0000:00:05.0 > /sys/bus/pci/drivers/igb_uio/bind > -bash: echo: write error: No such device >=20 > Due to this the bind fails and the virtio_pmd is not able to take and my = app is > not coming up. > EAL: PCI device 0000:00:03.0 on NUMA socket -1 > EAL: probe driver: 1af4:1000 rte_virtio_pmd > EAL: 0000:00:06.0 not managed by UIO driver, skipping > EAL: Error - exiting with code: 1 > Cause: No Ethernet ports - bye >=20 > I see lots of email threads on similar issue but none had the final concl= usion. > So can someone guide me on how to proceed further or get out of this erro= r. >=20 Suggest you use the dpdk_nic_bind.py in recently released dpdk package or g= et it from dpdk.org repo. I use it to bind virtio-pci device to igb_uio and after that, I bind it rev= ersely from igb_uio back to virtio-pci again. It works, don't find any issue. =20 Thanks Changchun