From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 7D6B71B21D for ; Mon, 21 May 2018 19:05:41 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 May 2018 10:05:40 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,426,1520924400"; d="scan'208,217";a="43012732" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by orsmga008.jf.intel.com with ESMTP; 21 May 2018 10:05:39 -0700 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 21 May 2018 10:05:39 -0700 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.235]) by FMSMSX154.amr.corp.intel.com ([169.254.6.14]) with mapi id 14.03.0319.002; Mon, 21 May 2018 10:05:38 -0700 From: "Wiles, Keith" To: Milad Arabi CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Found 0 usable devices Thread-Index: AQHT8Od0arwRuLt6EUCyS9rGOcoKLqQ6mewAgAA31QCAAAKSAIAABHsAgAAGmwA= Date: Mon, 21 May 2018 17:05:37 +0000 Message-ID: <4F08114D-CD95-41B0-8605-0EE61C99FA17@intel.com> References: <5CE156A7-6529-4F5C-BF7E-AFB6A2C2E95D@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.53.246] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Found 0 usable devices X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2018 17:05:42 -0000 On May 21, 2018, at 11:41 AM, Milad Arabi > wrote: Since I do not know anything about Eng-Sample NIC then no it's not. It is t= he original Intel network card pass through to CentOS from VMware. Do you think maybe the VMware cause this issue? Could be, guess its back to google for passthru NICs in VMWare or how to se= t the NIC MAC address in VMWare. On Mon, May 21, 2018 at 8:55 PM, Wiles, Keith > wrote: On May 21, 2018, at 11:16 AM, Milad Arabi > wrote: Hi Keith Thank you for your reply. Could you please check my output at: https://asciinema.org/a/182678 I get this error: PMD: eth_ixgbe_dev_init(): The EEPROM checksum is not valid: -1 Normally that means this is a Eng-Sample NIC, is it? If it is then we have to find someone to program the EPROM to setup the NIC= . That is about all I know. any comment would be appreciated On Mon, May 21, 2018 at 5:26 PM, Wiles, Keith > wrote: > On May 21, 2018, at 4:37 AM, Milad Arabi > wrote: > > Hi there > I try to with dpdk 17.08 on centos7.5 with other library,but I got this: > >> [INFO] Initializing DPDK. This will take a few seconds... >> EAL: Detected 16 lcore(s) >> EAL: Probing VFIO support... >> EAL: PCI device 0000:0b:00.0 on NUMA socket -1 >> EAL: Invalid NUMA socket, default to 0 >> EAL: probe driver: 15ad:7b0 net_vmxnet3 >> EAL: PCI device 0000:13:00.0 on NUMA socket 1 >> EAL: probe driver: 8086:10fb net_ixgbe >> EAL: PCI device 0000:13:00.1 on NUMA socket -1 >> EAL: Invalid NUMA socket, default to 0 >> EAL: probe driver: 8086:10fb net_ixgbe >> *[INFO] Found 0 usable devices:* > > > are these errors come from dpdk? and how I can solve this problem? Did you use the dpdk-devbind.py tool in dpdk to bind the device to allow DP= DK to use the device? Also you may have to insmod the igb_uio.ko for pci_uio_generic modules in t= he kernel? > > # ethtool -i ens224f1 >> driver: ixgbe >> version: 5.3.7 >> firmware-version: 0x80000835, 1.949.0 >> expansion-rom-version: >> bus-info: 0000:13:00.1 >> supports-statistics: yes >> supports-test: yes >> supports-eeprom-access: yes >> supports-register-dump: yes >> supports-priv-flags: yes Regards, Keith Regards, Keith Regards, Keith