From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id F21027E99 for ; Thu, 23 Oct 2014 07:45:05 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 22 Oct 2014 22:52:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,773,1406617200"; d="scan'208";a="623754785" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by orsmga002.jf.intel.com with ESMTP; 22 Oct 2014 22:52:51 -0700 Received: from kmsmsx151.gar.corp.intel.com (172.21.73.86) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 23 Oct 2014 13:52:11 +0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by KMSMSX151.gar.corp.intel.com (172.21.73.86) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 23 Oct 2014 13:52:11 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.207]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.44]) with mapi id 14.03.0195.001; Thu, 23 Oct 2014 13:52:10 +0800 From: "Dong, Binghua" To: Lilijun , "Zhang, Helin" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver Thread-Index: AQHP7nLuQqnAO4b4ski4Gf0DVjUfcJw8hGkAgAAM3wCAAJwNoA== Date: Thu, 23 Oct 2014 05:52:10 +0000 Message-ID: <87AA51EDE124984B9C1CABE77679F9B2117CC6B8@SHSMSX103.ccr.corp.intel.com> References: <544877B0.4030905@huawei.com> <54488484.8030700@huawei.com> In-Reply-To: <54488484.8030700@huawei.com> 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] Problems when testing l2fwd with ixgbevf pmd dirver 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: Thu, 23 Oct 2014 05:45:06 -0000 Hi all, It looks like that Lilijun runs the four steps are both in HOST? Lilijun, you did not startup a VM, pass through the VF to VM, and runs l2fw= d in VM? -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lilijun Sent: Thursday, October 23, 2014 12:31 PM To: Zhang, Helin; dev@dpdk.org Subject: Re: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver On 2014/10/23 11:44, Zhang, Helin wrote: > Hi >=20 >> -----Original Message----- >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lilijun >> Sent: Thursday, October 23, 2014 11:36 AM >> To: dev@dpdk.org >> Subject: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver >> >> Hi all, >> >> I am testing the example l2fwd of dpdk-1.7.0 using intel 82599 VF NICs. >> But the VF can't be used when doing probe pmd driver with following erro= r: >> >> EAL: PCI device 0000:02:10.0 on NUMA socket -1 >> EAL: probe driver: 8086:10ed rte_ixgbevf_pmd >> EAL: PCI memory mapped at 0x7f78b181f000 >> EAL: PCI memory mapped at 0x7f78b181b000 >> EAL: Error - exiting with code: 1 >> Cause: Requested device 0000:02:10.0 cannot be used >> >> Any suggestions? > Did you launch DPDK host application? My test steps: 1) rmmod ixgbe; modprobe ixgbe max_vfs=3D3,3 2) insmod dpdk-1.7.0/x86_64-native-linuxapp-gcc/kmod/igb_uio.ko 3) dpdk_nic_bind.py -b igb_uio 02:10.0 02:10.1 4) ./build/l2fwd -c 0xf -n 3 -- -p 3 -q 1 Then l2fwd run failed with error messages shown as above email. Is my test steps correctly? >=20 >> >> Thanks, >> Jerry >=20 > Regards, > Helin >=20 >=20