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 7A587567F for ; Fri, 12 May 2017 17:25:06 +0200 (CEST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 May 2017 08:25:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,330,1491289200"; d="scan'208";a="100742862" Received: from orsmsx110.amr.corp.intel.com ([10.22.240.8]) by fmsmga005.fm.intel.com with ESMTP; 12 May 2017 08:25:05 -0700 Received: from orsmsx160.amr.corp.intel.com (10.22.226.43) by ORSMSX110.amr.corp.intel.com (10.22.240.8) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 12 May 2017 08:25:04 -0700 Received: from orsmsx104.amr.corp.intel.com ([169.254.4.118]) by ORSMSX160.amr.corp.intel.com ([169.254.13.69]) with mapi id 14.03.0319.002; Fri, 12 May 2017 08:25:04 -0700 From: "Mastorakis, Spyridon" To: "Richardson, Bruce" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] "Port 0 is not present on the board" when building DPDK libraries as shared Thread-Index: AdLKne0KF7mx7AQaS0WgJknEwZpOjgAmElyAAAEBTDA= Date: Fri, 12 May 2017 15:25:03 +0000 Message-ID: <84F194B655461746B15919D288BD7AB02879D6@ORSMSX104.amr.corp.intel.com> References: <84F194B655461746B15919D288BD7AB02877EB@ORSMSX104.amr.corp.intel.com> <20170512084124.GA53020@bricha3-MOBL3.ger.corp.intel.com> In-Reply-To: <20170512084124.GA53020@bricha3-MOBL3.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.22.254.140] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] "Port 0 is not present on the board" when building DPDK libraries as shared X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2017 15:25:07 -0000 Hi Bruce, Thank you for your response. This seems to have resolved the issue. Spyros -----Original Message----- From: Richardson, Bruce=20 Sent: Friday, May 12, 2017 1:41 AM To: Mastorakis, Spyridon Cc: dev@dpdk.org Subject: Re: [dpdk-dev] "Port 0 is not present on the board" when building = DPDK libraries as shared On Thu, May 11, 2017 at 09:33:32PM +0000, Mastorakis, Spyridon wrote: > Hi guys, >=20 > When I compile the DPDK libraries as shared (by modifying the base_config= file) and try to run an application (e.g., l3fwd), I get an error that por= t 0 is not present on board. >=20 > I have cleaned the system several times (unbinded NICs, removed igb_uio a= nd uio modules and hugepage mappings) and have configured everything again,= but this does not resolve the issue. I am also not able to add a virtual d= evice (specifically a virtual ring) when I compile as a shared library (no = PMD drivers found). >=20 > When I compile the DPDK libraries as static though, everything works perf= ectly fine and I can run the DPDK applications and add virtual rings. >=20 > I have tried dpdk-17.02 and the latest stable dpdk version (16.11.1), but= none of them seems to work. >=20 > Do you have any clue why this is happening? >=20 > Thank you in advance, > Spyros When compiled as a shared lib, are you passing in the "-d" parameters to ma= ke sure that the PMDs are actually loaded by the app. Unlike the static ver= sion, they are not automatically linked in the shared lib build. /Bruce