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 B716E7E9D for ; Thu, 23 Oct 2014 07:30:33 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 22 Oct 2014 22:38:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,773,1406617200"; d="scan'208";a="618990013" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by fmsmga002.fm.intel.com with ESMTP; 22 Oct 2014 22:38:54 -0700 Received: from kmsmsx153.gar.corp.intel.com (172.21.73.88) 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:37:24 +0800 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by KMSMSX153.gar.corp.intel.com (172.21.73.88) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 23 Oct 2014 13:37:24 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.207]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.202]) with mapi id 14.03.0195.001; Thu, 23 Oct 2014 13:37:23 +0800 From: "Dong, Binghua" To: Lilijun , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Problems when testing l2fwd with ixgbevf pmd dirver Thread-Index: AQHP7nLuQqnAO4b4ski4Gf0DVjUfcJw9J6iw Date: Thu, 23 Oct 2014 05:37:22 +0000 Message-ID: <87AA51EDE124984B9C1CABE77679F9B2117CC675@SHSMSX103.ccr.corp.intel.com> References: <544877B0.4030905@huawei.com> In-Reply-To: <544877B0.4030905@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:30:34 -0000 Hi Lilijun, I think you need unbind the device 02:10.0 from driver ixgbevf first; In Ho= st Linux, you also need ifconfig up the PF eth of this VF; Please ref my script to unbind a VF device and pass into VM, such as: PCI_eth=3D"0000:02:10.0" ID_eth=3D"ffff ffff" PCIX_eth=3D" -device pci-assign,host=3D"${PCI_eth} echo $ID_eth > /sys/bus/pci/drivers/pci-stub/new_id echo ${PCI_eth} > /sys/bus/pci/devices/${PCI_eth}/driver/unbind echo ${PCI_eth} > /sys/bus/pci/drivers/pci-stub/bind CMD=3D${CMD}${PCIX_eth} =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=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=3D=3D=3D=3D=3D=3D #!/bin/bash ID=3D"8086 0442" PCI=3D"0000:83:01" IMG=3D"/root/test_image/sles11sp2.img" HOST=3D" -vnc 172.16.200.166:1 " PCIX=3D" -device pci-assign,host=3D"${PCI} CDROM=3D" -cdrom /root/QAT/driver.iso " CMD=3D"qemu-system-x86_64 -m 2048 -smp 4 -hda "${IMG}${HOST}" -enable-kvm " #ADD CCK if [ 1 -eq 0 ];then echo $ID > /sys/bus/pci/drivers/pci-stub/new_id for i in 4 5 6 7 do echo ${PCI}"."$i > /sys/bus/pci/devices/${PCI}"."$i/driver/unbind echo ${PCI}"."$i > /sys/bus/pci/drivers/pci-stub/bind CMD=3D${CMD}${PCIX}.$i done fi #ADD ETH if [ 1 -eq 0 ];then PCI_eth=3D"0000:02:00.1" ID_eth=3D"8086 1521" PCIX_eth=3D" -device pci-assign,host=3D"${PCI_eth} echo $ID_eth > /sys/bus/pci/drivers/pci-stub/new_id echo ${PCI_eth} > /sys/bus/pci/devices/${PCI_eth}/driver/unbind echo ${PCI_eth} > /sys/bus/pci/drivers/pci-stub/bind CMD=3D${CMD}${PCIX_eth} fi #ADD CDROM #CMD=3D${CMD}${CDROM} echo $CMD #rmmod kvm_intel #rmmod kvm modprobe kvm modprobe kvm_intel $CMD -----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 error: 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? Thanks, Jerry