From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by dpdk.org (Postfix) with ESMTP id C37B668D0 for ; Fri, 10 May 2013 03:00:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4024; q=dns/txt; s=iport; t=1368147654; x=1369357254; h=from:to:subject:date:message-id:mime-version; bh=jhixihbwVIFqiXCi94zvwrXliGtEhQ2NNO/h45Du8E4=; b=P/qUxH0X5rICYIWNHquLur3wkq2CBm2GvpBTd7CjVThTzHk+0CZzeNwi q7urCM2D5piRn6M7nXvuk6kYJOMcemg0FbzqxKnpktmwdRR9HdwM0nJy0 qst69VO5DflK/ndupiZqpDxlOP7XHKPP610Kv/AfDJvpfF2KW71sQXSxG w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AikFAM9FjFGtJXG9/2dsb2JhbABSgkNEN8APexZtB4IhAQQtXgEMHlYXDwEEG4gEDJ18oBSOd4MsYQOhPYckgw+CJw X-IronPort-AV: E=Sophos;i="4.87,645,1363132800"; d="scan'208,217";a="205614461" Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-9.cisco.com with ESMTP; 10 May 2013 01:00:53 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4A10rdq030213 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 10 May 2013 01:00:53 GMT Received: from xmb-aln-x05.cisco.com ([169.254.11.52]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Thu, 9 May 2013 20:00:53 -0500 From: "Rui Vaz (ruvaz)" To: "dev@dpdk.org" Thread-Topic: rte_eth_dev_count() returns 0 Thread-Index: Ac5NGdCGcNgOn+wOTd+gA1mYCiqrWg== Date: Fri, 10 May 2013 01:00:52 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.154.212.55] Content-Type: multipart/alternative; boundary="_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2EA0Dxmbalnx05ciscoc_" MIME-Version: 1.0 Subject: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 01:00:53 -0000 --_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2EA0Dxmbalnx05ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi dev-dpdk, I am following a Intel DPDK Step by Step Instruction found here: http://www= .slideshare.net/hisaki/intel-dpdk-step-by-step-instructions My Hello app from the DPDK examples runs fine, but I get the following erro= r when running the l2fwd app: "EAL: Error - exiting with code: 1 Cause: no Ethernet ports - bye" The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Virtual Mac= hine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon E5-260= 0. I would really appreciate If you could provide some help to solve this issu= e. Thank you, Rui --_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2EA0Dxmbalnx05ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi dev-dpdk,

 

I am following a Intel DPDK Step by Step Instruction= found here: http://www.slideshare.net/hisaki/intel-dpdk-step-by-step-instruction= s

My Hello app from the DPDK examples runs fine, but I= get the following error when running the l2fwd app:

 

“EAL: Error – exiting with code: 1<= /o:p>

Cause: no Ethernet ports – bye”

 

The rte_eth_dev_count() call returns 0, I am using a= CentOS 6.3 Virtual Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which= comes with Xeon E5-2600.  

 

I would really appreciate If you could provide some = help to solve this issue.

 

Thank you,

Rui

 

--_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2EA0Dxmbalnx05ciscoc_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by dpdk.org (Postfix) with ESMTP id 22AEE68D0 for ; Fri, 10 May 2013 17:47:19 +0200 (CEST) Received: by mail-we0-f177.google.com with SMTP id q58so4101719wes.36 for ; Fri, 10 May 2013 08:47:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=UMdGJELLaeMtIQrS6SiqBF+ukt1umlaJsqVOyp9bEnw=; b=CaT3YAAmDlZqGekIyH2uO0VZZ3Fh8uaoRsOJLqqYOfg/YuBUmI5RcFGjf4vy47NPVd f9pIQyiVlJ1jrLYTQoy0VtDyN8Ys68St9rE5EppcYke+AClZJx/qgkS9Wmx7FJ1EIBs1 n0uAZJNXkYvOvgbb21ZsXurR41Z0+39lqdpQvCk0eMhM6qO1o81uWWNr7iZGlaGseGb8 iMDRJgOinuKKLMhMXuML4gAoOJ6GalI3TzO7pgdp63OJzwgy5vj52C87MS7IKobJ9p0L a596qb1nlJwK/usPSHnlmxKSnghViQLq16CNhE+/VgErsqiwV5F7nHJt4Xi2UhEwrnCT ahpQ== X-Received: by 10.194.240.132 with SMTP id wa4mr25596190wjc.52.1368200840109; Fri, 10 May 2013 08:47:20 -0700 (PDT) Received: from saturne.dev.6wind.com (scp68-1-78-242-96-17.fbx.proxad.net. [78.242.96.17]) by mx.google.com with ESMTPSA id ek7sm4279606wic.4.2013.05.10.08.47.18 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 10 May 2013 08:47:19 -0700 (PDT) Message-ID: <518D1685.20500@6wind.com> Date: Fri, 10 May 2013 17:47:17 +0200 From: Vincent JARDIN Organization: www.6wind.com User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: dev@dpdk.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkUZSpCui3pqLOOPMcmG5C4sWpvPUSnKAuGm6BP4QQ+ik6coC2Pqbzbjg9s8qtMwNw6Am9m Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 15:47:19 -0000 > The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Virtual > Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon > E5-2600. Can you run lspci -vt and send us the output? Best regards, Vincent From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailgate.neusoft.com (mailgate.neusoft.com [210.83.25.69]) by dpdk.org (Postfix) with ESMTP id 6C44468D0 for ; Fri, 10 May 2013 03:18:30 +0200 (CEST) X-IronPort-AV: E=McAfee;i="5400,1158,7070"; a="103222796" Received: from unknown (HELO mailgate8.neusoft.com) ([192.168.1.132]) by mailgate.neusoft.com with ESMTP/TLS/DES-CBC3-SHA; 10 May 2013 09:18:28 +0800 Received: from unknown (HELO smtp.neusoft.com) ([192.168.2.143]) by mailgate8.neusoft.com with ESMTP/TLS/AES128-SHA; 10 May 2013 09:18:28 +0800 Received: from mail-oa0-f45.google.com (209.85.219.45) by MPS-SYHUB03.neusoft.internal (192.168.2.143) with Microsoft SMTP Server (TLS) id 14.2.247.3; Fri, 10 May 2013 09:18:27 +0800 Received: by mail-oa0-f45.google.com with SMTP id j6so3267233oag.18 for ; Thu, 09 May 2013 18:18:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=fPcVZld45ALaJsP38KBZWu5XSpYnyQr8IjaVrUaAmOM=; b=CVJyUtobENKgeVuwAswNSgJKzH9DidId9I8GGENIIWxnkUdh8eHYF0B99UFmxFIALD 6Ls1UirKvRUOE5EcN+6u+UUeNuoSI7hWOhyUGh/mb1c66Hd0e6YooHUF+QBzT/hQjT9m S6PnIXA/AcpdLl7yr5pc95GbZik95nkGHieJ3nxWc7SVuDET4kMgJptvreUJIvxqks/g qWJz2ou/WQFrajKjIkzSJHiell1+yeBzRqtH5fII+djQe+TeiR/Cl8GS53Owg4KHn2Kp D9ND+V1ZSfGBSq3ohbGBu5Z6GOdEVHMZKHQh9j1+Zse7iVUZjw3nUFR9geUy1TOglzr8 U8gQ== X-Received: by 10.60.124.100 with SMTP id mh4mr5696958oeb.41.1368148704264; Thu, 09 May 2013 18:18:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.153.4 with HTTP; Thu, 9 May 2013 18:18:04 -0700 (PDT) In-Reply-To: References: From: Henry Wang Date: Fri, 10 May 2013 09:18:04 +0800 Message-ID: To: "Rui Vaz (ruvaz)" Content-Type: multipart/alternative; boundary="047d7b5d300c848b9c04dc52f19a" X-Originating-IP: [209.85.219.45] X-Mailman-Approved-At: Fri, 10 May 2013 17:48:30 +0200 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 01:18:32 -0000 --047d7b5d300c848b9c04dc52f19a Content-Type: text/plain; charset="windows-1252" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable As far as I known, DPDK(1.2.3) only supports the following NICs: (1) Intel 82576, 82580, I350 chipset based NICs; (2) Intel 82599, X540T, X520T chipset based NICs; (3) virtual NICs generated by SR-IOV from (2). If the NICs on your C220 M3 is one of (2), you can run l2fwdvf OR l3fwdvf successfully with SR-IOV enabled in ESXi. And I do not know wheather ESXi 5.0 VMM has SR-IOV function or not. Further more, please reference to DPDK release notes. http://www.intel.com/content/dam/www/public/us/en/documents/release-notes/i= ntel-dpdk-release-notes.pdf On Fri, May 10, 2013 at 9:00 AM, Rui Vaz (ruvaz) wrote: > Hi dev-dpdk,**** > > ** ** > > I am following a Intel DPDK Step by Step Instruction found here: > http://www.slideshare.net/hisaki/intel-dpdk-step-by-step-instructions**** > > My Hello app from the DPDK examples runs fine, but I get the following > error when running the l2fwd app:**** > > ** ** > > =93EAL: Error =96 exiting with code: 1**** > > Cause: no Ethernet ports =96 bye=94**** > > ** ** > > The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Virtual > Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon > E5-2600. **** > > ** ** > > I would really appreciate If you could provide some help to solve this > issue.**** > > ** ** > > Thank you,**** > > Rui**** > > ** ** > ---------------------------------------------------------------------------= ------------------------ Confidentiality Notice: The information contained in this e-mail and any ac= companying attachment(s) = is intended only for the use of the intended recipient and may be confident= ial and/or privileged of = Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader = of this communication is = not the intended recipient, unauthorized use, forwarding, printing, storin= g, disclosure or copying = is strictly prohibited, and may be unlawful.If you have received this commu= nication in error,please = immediately notify the sender by return e-mail, and delete the original mes= sage and all copies from = your system. Thank you. = ---------------------------------------------------------------------------= ------------------------ --047d7b5d300c848b9c04dc52f19a Content-Type: text/html; charset="windows-1252" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable
= As far as I known, DPDK(1.2.3) only supports the following NICs:
(1) Intel 82576, 82580, I350 chipset based NICs;
(2) Intel 82599, X540T, X520T chipset based NICs;
(3) virtual NICs generated by SR-IOV from (2).

If the NICs on your C220 M3 is one o= f (2), you can run l2fwdvf OR l3fwdvf successfully with SR-IOV enabled in E= SXi.
And I do not know wheather ESXi 5.0 = VMM has SR-IOV function or not.

Further= more, please reference to DPDK release notes.



On Fri, May 10, 2013 at 9:00 AM= , Rui Vaz (ruvaz) <ruvaz@cisco.com> wrote:

Hi dev-dpdk,

=A0

I am following a Intel DPDK Step by Step Instruction= found here: http://www.slideshare.net/hisaki/intel-dpdk-step-b= y-step-instructions

My Hello app from the DPDK examples runs fine, but I= get the following error when running the l2fwd app:

=A0

=93EAL: Error =96 exiting with code: 1=

Cause: no Ethernet ports =96 bye=94

=A0

The rte_eth_dev_count() call returns 0, I am using a= CentOS 6.3 Virtual Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which= comes with Xeon E5-2600. =A0

=A0

I would really appreciate If you could provide some = help to solve this issue.

=A0

Thank you,

Rui

=A0


------------------------------------------------------------------------= ---------------------------
Confidentiality Notice: The information contained in this e-mail and any ac= companying attachment(s)
is intended only for the use of the intended recipient and may be confident= ial and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader = of this communication is
not the intended recipient, unauthorized use, forwarding, printing,  s= toring, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this commu= nication in error,please
immediately notify the sender by return e-mail, and delete the original mes= sage and all copies from
your system. Thank you.
---------------------------------------------------------------------------= ------------------------

--047d7b5d300c848b9c04dc52f19a-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) by dpdk.org (Postfix) with ESMTP id 6DA1968E2 for ; Fri, 10 May 2013 18:05:08 +0200 (CEST) Received: from sc9-mailhost1.vmware.com (sc9-mailhost1.vmware.com [10.113.161.71]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 84255287DC; Fri, 10 May 2013 09:05:08 -0700 (PDT) Received: from zcs-prod-mta-3.vmware.com (zcs-prod-mta-3.vmware.com [10.113.163.65]) by sc9-mailhost1.vmware.com (Postfix) with ESMTP id 7751C18756; Fri, 10 May 2013 09:05:08 -0700 (PDT) Received: from zcs-prod-mta-3.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-mta-3.vmware.com (Postfix) with ESMTP id 6CD43E0132; Fri, 10 May 2013 09:05:08 -0700 (PDT) Received: from zcs-prod-mbox-7.vmware.com (lbv-sc9-t2prod2-int.vmware.com [10.113.160.246]) by zcs-prod-mta-3.vmware.com (Postfix) with ESMTP; Fri, 10 May 2013 09:05:08 -0700 (PDT) Date: Fri, 10 May 2013 09:05:08 -0700 (PDT) From: Bhavesh Davda To: Henry Wang Message-ID: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5291866_1539894212.1368201908282" X-Originating-IP: [10.113.163.67] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC26 (Mac)/8.0.3_GA_5664) Thread-Topic: rte_eth_dev_count() returns 0 Thread-Index: GhbSsSPm770mmNv58PZXwfF4Zp5QWw== Cc: dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 16:05:09 -0000 ------=_Part_5291866_1539894212.1368201908282 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable ESXi 5.0 doesn't have SR-IOV support (it's in the code, but is disabled and= not usable for customers). VMware introduced SR-IOV support, including out= of the box support for Intel Niantic 10GbE NICs, in ESXi 5.1.=20 --=20 Bhavesh Davda=20 ----- Original Message ----- > From: "Henry Wang" > To: "Rui Vaz (ruvaz)" > Cc: dev@dpdk.org > Sent: Thursday, May 9, 2013 6:18:04 PM > Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 > As far as I known, DPDK(1.2.3) only supports the following NICs: > (1) Intel 82576, 82580, I350 chipset based NICs; > (2) Intel 82599, X540T, X520T chipset based NICs; > (3) virtual NICs generated by SR-IOV from (2). > If the NICs on your C220 M3 is one of (2), you can run l2fwdvf OR l3fwdvf > successfully with SR-IOV enabled in ESXi. > And I do not know wheather ESXi 5.0 VMM has SR-IOV function or not. > Further more, please reference to DPDK release notes. > http://www.intel.com/content/dam/www/public/us/en/documents/release-notes= /intel-dpdk-release-notes.pdf > On Fri, May 10, 2013 at 9:00 AM, Rui Vaz (ruvaz) < ruvaz@cisco.com > wrot= e: > > Hi dev-dpdk, >=20 > > I am following a Intel DPDK Step by Step Instruction found here: > > http://www.slideshare.net/hisaki/intel-dpdk-step-by-step-instructions >=20 > > My Hello app from the DPDK examples runs fine, but I get the following > > error > > when running the l2fwd app: >=20 > > =E2=80=9CEAL: Error =E2=80=93 exiting with code: 1 >=20 > > Cause: no Ethernet ports =E2=80=93 bye=E2=80=9D >=20 > > The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Virtual > > Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon > > E5-2600. >=20 > > I would really appreciate If you could provide some help to solve this > > issue. >=20 > > Thank you, >=20 > > Rui >=20 > -------------------------------------------------------------------------= -------------------------- > Confidentiality Notice: The information contained in this e-mail and any > accompanying attachment(s) > is intended only for the use of the intended recipient and may be > confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reade= r of > this communication is > not the intended recipient, unauthorized use, forwarding, printing, stori= ng, > disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this > communication in error,please > immediately notify the sender by return e-mail, and delete the original > message and all copies from > your system. Thank you. > -------------------------------------------------------------------------= -------------------------- ------=_Part_5291866_1539894212.1368201908282 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
ESXi 5.0 doesn't have SR-IOV sup= port (it's in the code, but is disabled and not usable for customers). VMwa= re introduced SR-IOV support, including out of the box support for Intel Ni= antic 10GbE NICs, in ESXi 5.1.

--
Bhavesh Davda


From: "Henry Wang" <wang_hr@neusoft.com>
To: "Rui= Vaz (ruvaz)" <ruvaz@cisco.com>
Cc: dev@dpdk.org
Sent= : Thursday, May 9, 2013 6:18:04 PM
Subject: Re: [dpdk-dev] rt= e_eth_dev_count() returns 0

As far as I known, DPDK(1.2.3) only= supports the following NICs:
(1) Intel 82576, 82580, I350 chipset based NICs;
(2) Intel 82599, X540T, X520T chipset based NICs;
(3) virtual NICs generated by SR-IOV from (2).

If the NICs on your C220 M3 is one o= f (2), you can run l2fwdvf OR l3fwdvf successfully with SR-IOV enabled in E= SXi.
And I do not know wheather ESXi 5.0 = VMM has SR-IOV function or not.

Further= more, please reference to DPDK release notes.



On Fri, May 10, 2013= at 9:00 AM, Rui Vaz (ruvaz) <ruvaz@cisco.com> wrote:

Hi dev-dpdk,<= /span>

 =

I am following a Intel DPDK Step by Step Instruction= found here: http://www.slideshare.net/hisaki/intel-dpdk-step-b= y-step-instructions

My Hello app from the DPDK examples runs fine, but I= get the following error when running the l2fwd app:=

 =

=E2=80=9CEAL: Error =E2=80=93 exiting with code: 1

Cause: no Ethernet ports =E2=80=93 bye=E2=80=9D

 =

The rte_eth_dev_count() call returns 0, I am using a= CentOS 6.3 Virtual Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which= comes with Xeon E5-2600.  

 =

I would really appreciate If you could provide some = help to solve this issue.

 =

Thank you,

Rui

 =


------------------------------------------------------------------------= ---------------------------
Confidentiality Notice: The information contained in this e-mail and any ac= companying attachment(s)
is intended only for the use of the intended recipient and may be confident= ial and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader = of this communication is
not the intended recipient, unauthorized use, forwarding, printing,  s= toring, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this commu= nication in error,please
immediately notify the sender by return e-mail, and delete the original mes= sage and all copies from
your system. Thank you.
---------------------------------------------------------------------------= ------------------------


------=_Part_5291866_1539894212.1368201908282-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by dpdk.org (Postfix) with ESMTP id B68166A96 for ; Fri, 10 May 2013 18:15:52 +0200 (CEST) Received: by mail-pb0-f43.google.com with SMTP id md12so2898512pbc.30 for ; Fri, 10 May 2013 09:15:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type :content-transfer-encoding:x-gm-message-state; bh=sUsFIP79lArjoqpwOVPihAxwd/xxTQ4LCXscR35AOq8=; b=R1wEoznjsNxn4LWAJ6YSPUSn3n95MC3+GbEZnnOZvwM/uXdGiunbL82JHVUpA/p81C MWJj8+zmhAiPwf59psrO9kIcbxQW6W85NnRNxmvRghtrBHswDcyV5d6KBqUHB7we8g/z +E41Ll/LTHOreeCnZsoib1wNouOxL9C8K6deLXYbReE2AIhlLd0a3kCp3hky49sM4PQD 1y11BBR9VktgRPPt9QZ5lIt8Pr+h9XT+S4XObDQNwk0J0iLCL2qECLfOLcr1pV4ActHq Im5hHH3XawvJbHkYlVMTjyxE4OB1Jopjlm1Yi0csCz8l6DgdvOPIBgNE4/aif4AiJh7g GQEw== X-Received: by 10.66.27.197 with SMTP id v5mr18323123pag.211.1368202553529; Fri, 10 May 2013 09:15:53 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-71-109.bvtn.or.frontiernet.net. [50.53.71.109]) by mx.google.com with ESMTPSA id vz8sm3452157pac.20.2013.05.10.09.15.52 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 10 May 2013 09:15:53 -0700 (PDT) Date: Fri, 10 May 2013 09:15:49 -0700 From: Stephen Hemminger To: Bhavesh Davda Message-ID: <20130510091549.3c064df6@nehalam.linuxnetplumber.net> In-Reply-To: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> References: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlkxQewrF04kn3XO4xnOa+wPJSYOYtMb6SkxW5nxCvtFjWuFJ/r65XzKNKrZF9Hh8aB6rcL Cc: Henry Wang , dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 16:15:53 -0000 On Fri, 10 May 2013 09:05:08 -0700 (PDT) Bhavesh Davda wrote: > ESXi 5.0 doesn't have SR-IOV support (it's in the code, but is disabled and not usable for customers). VMware introduced SR-IOV support, including out of the box support for Intel Niantic 10GbE NICs, in ESXi 5.1. > You can use PCI passthrough (Directpath) on 5.0 (and 5.1). I found that SR-IOV on Vmware is even more fussy than SR-IOV on Linux. It requires a supported platform with VT-d and PCIe ASPM. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [208.91.2.13]) by dpdk.org (Postfix) with ESMTP id C2E686966 for ; Fri, 10 May 2013 18:21:35 +0200 (CEST) Received: from sc9-mailhost1.vmware.com (sc9-mailhost1.vmware.com [10.113.161.71]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 6EAAF283F5; Fri, 10 May 2013 09:21:36 -0700 (PDT) Received: from zcs-prod-mta-1.vmware.com (zcs-prod-mta-1.vmware.com [10.113.163.63]) by sc9-mailhost1.vmware.com (Postfix) with ESMTP id 6C64E18819; Fri, 10 May 2013 09:21:36 -0700 (PDT) Received: from zcs-prod-mta-1 (localhost.localdomain [127.0.0.1]) by zcs-prod-mta-1.vmware.com (Postfix) with ESMTP id 58627E00FB; Fri, 10 May 2013 09:21:36 -0700 (PDT) Received: from zcs-prod-mbox-7.vmware.com (lbv-sc9-t2prod2-int.vmware.com [10.113.160.246]) by zcs-prod-mta-1.vmware.com (Postfix) with ESMTP; Fri, 10 May 2013 09:21:36 -0700 (PDT) Date: Fri, 10 May 2013 09:21:36 -0700 (PDT) From: Bhavesh Davda To: Stephen Hemminger Message-ID: <525534677.5312512.1368202896189.JavaMail.root@vmware.com> In-Reply-To: <20130510091549.3c064df6@nehalam.linuxnetplumber.net> References: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> <20130510091549.3c064df6@nehalam.linuxnetplumber.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.163.67] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC26 (Mac)/8.0.3_GA_5664) Thread-Topic: rte_eth_dev_count() returns 0 Thread-Index: uSfyTSR6cecWTOaUEfinyUJsXavuTA== Cc: Henry Wang , dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 16:21:36 -0000 Right: VMware has supported VMDirectPath passthrough since ESXi 4.0, on any platform with an IOMMU (Intel VT-d) which is anything Nehalem Xeons or newer. I know this is a DPDK forum, but Stephen, if you know of specific limitations of ESXi 5.1's SR-IOV support, please let me know and I'll make sure we work on addressing them. -- Bhavesh Davda ----- Original Message ----- > From: "Stephen Hemminger" > To: "Bhavesh Davda" > Cc: "Henry Wang" , dev@dpdk.org > Sent: Friday, May 10, 2013 9:15:49 AM > Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 > > On Fri, 10 May 2013 09:05:08 -0700 (PDT) > Bhavesh Davda wrote: > > > ESXi 5.0 doesn't have SR-IOV support (it's in the code, but is disabled and > > not usable for customers). VMware introduced SR-IOV support, including out > > of the box support for Intel Niantic 10GbE NICs, in ESXi 5.1. > > > > You can use PCI passthrough (Directpath) on 5.0 (and 5.1). > I found that SR-IOV on Vmware is even more fussy than SR-IOV on Linux. > It requires a supported platform with VT-d and PCIe ASPM > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by dpdk.org (Postfix) with ESMTP id F03EF6A9E for ; Fri, 10 May 2013 20:45:10 +0200 (CEST) Received: by mail-pa0-f46.google.com with SMTP id fa10so3143007pad.19 for ; Fri, 10 May 2013 11:45:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type :content-transfer-encoding:x-gm-message-state; bh=8JydxChKHj28ARLCDBWpPGWpzJQlqyfG/8Xdy5u8Vro=; b=dFG5ic+1mGQRdIKxPRmKK7GhS7xQEMGKMBCgdO8Oj3e2+lwsYn9XQbA6vqe9FSEbep 0xtifoD0VYnIy2P6oLMzJmv42q1kfRM9HXz6cDt0wVBlxSiWoj7moaU4NQkBAZ14/OtQ 0foEc045ku9V2vrtNa4ApIh3eXsQNXbPhoRYdnZFGXzBmobeKuWcEuVxABfJ02LmjJQF SAngdJSGNh02svExtr5qFEU4Zb9TjKohdl29dfhgWCfp0Xi0TTX7F59LY9PcXEY5TWGD oVvxgkfNKXJQGOIS7dbrDexioDeXi4NA9x3IdySOGIRvYhBOAdgnidVjidEnTumHM7Sv QTDA== X-Received: by 10.68.172.36 with SMTP id az4mr18315911pbc.211.1368211510946; Fri, 10 May 2013 11:45:10 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-71-109.bvtn.or.frontiernet.net. [50.53.71.109]) by mx.google.com with ESMTPSA id zo4sm3619694pbc.21.2013.05.10.11.45.09 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 10 May 2013 11:45:10 -0700 (PDT) Date: Fri, 10 May 2013 11:44:50 -0700 From: Stephen Hemminger To: Bhavesh Davda Message-ID: <20130510114450.7104c5d2@nehalam.linuxnetplumber.net> In-Reply-To: <525534677.5312512.1368202896189.JavaMail.root@vmware.com> References: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> <20130510091549.3c064df6@nehalam.linuxnetplumber.net> <525534677.5312512.1368202896189.JavaMail.root@vmware.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlGKGWW2vlkIX60nZl5kB3zRtXLuUNmaFqVNZOIoGBPOtrVn/efZsJyFXXKtwXMxv2s4I3s Cc: Henry Wang , dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 18:45:11 -0000 On Fri, 10 May 2013 09:21:36 -0700 (PDT) Bhavesh Davda wrote: > Right: VMware has supported VMDirectPath passthrough since ESXi 4.0, on any platform with an IOMMU (Intel VT-d) which is anything Nehalem Xeons or newer. > > I know this is a DPDK forum, but Stephen, if you know of specific limitations of ESXi 5.1's SR-IOV support, please let me know and I'll make sure we work on addressing them. I had trouble getting it to work on a white box ASUS motherboard. It seems the MB didn't support PCIe power management ASPM. And Intel confirmed that was required by Vmware. Linux didn't care if ASPM wasn't available and worked fine with SR-IOV. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) by dpdk.org (Postfix) with ESMTP id D8C726AA0 for ; Fri, 10 May 2013 21:10:44 +0200 (CEST) Received: from sc9-mailhost3.vmware.com (sc9-mailhost3.vmware.com [10.113.161.73]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 6AE6E2807F; Fri, 10 May 2013 12:10:42 -0700 (PDT) Received: from zcs-prod-mta-1.vmware.com (zcs-prod-mta-1.vmware.com [10.113.163.63]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id 654A640076; Fri, 10 May 2013 12:10:42 -0700 (PDT) Received: from zcs-prod-mta-1 (localhost.localdomain [127.0.0.1]) by zcs-prod-mta-1.vmware.com (Postfix) with ESMTP id 52099E0109; Fri, 10 May 2013 12:10:42 -0700 (PDT) Received: from zcs-prod-mbox-7.vmware.com (lbv-sc9-t2prod2-int.vmware.com [10.113.160.246]) by zcs-prod-mta-1.vmware.com (Postfix) with ESMTP; Fri, 10 May 2013 12:10:42 -0700 (PDT) Date: Fri, 10 May 2013 12:10:42 -0700 (PDT) From: Bhavesh Davda To: Stephen Hemminger Message-ID: <69354296.5541435.1368213042137.JavaMail.root@vmware.com> In-Reply-To: <20130510114450.7104c5d2@nehalam.linuxnetplumber.net> References: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> <20130510091549.3c064df6@nehalam.linuxnetplumber.net> <525534677.5312512.1368202896189.JavaMail.root@vmware.com> <20130510114450.7104c5d2@nehalam.linuxnetplumber.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.163.67] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC26 (Mac)/8.0.3_GA_5664) Thread-Topic: rte_eth_dev_count() returns 0 Thread-Index: hAKcgoyJPq1wiOBLtmirrWvpYbhoiQ== Cc: Henry Wang , dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 19:10:45 -0000 Hi Stephen, I checked both our hypervisor code and with the experts who wrote and maintain the code, and we don't have any such limitation about not supporting SR-IOV if the motherboard or device doesn't support PCIe ASPM. If you can point me to the Intel person(s) who gave you that information (offline, no need to make this public :)), we can make sure such FUD doesn't continue getting spread too far. Thanks for making us aware of this FUD though. -- Bhavesh Davda ----- Original Message ----- > From: "Stephen Hemminger" > To: "Bhavesh Davda" > Cc: "Henry Wang" , dev@dpdk.org > Sent: Friday, May 10, 2013 11:44:50 AM > Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 > > On Fri, 10 May 2013 09:21:36 -0700 (PDT) > Bhavesh Davda wrote: > > > Right: VMware has supported VMDirectPath passthrough since ESXi 4.0, on any > > platform with an IOMMU (Intel VT-d) which is anything Nehalem Xeons or > > newer. > > > > I know this is a DPDK forum, but Stephen, if you know of specific > > limitations of ESXi 5.1's SR-IOV support, please let me know and I'll make > > sure we work on addressing them. > > I had trouble getting it to work on a white box ASUS motherboard. It seems > the MB didn't > support PCIe power management ASPM. And Intel confirmed that was required by > Vmware. > Linux didn't care if ASPM wasn't available and worked fine with SR-IOV > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by dpdk.org (Postfix) with ESMTP id E43616AA4 for ; Fri, 10 May 2013 21:29:32 +0200 (CEST) Received: by mail-pb0-f42.google.com with SMTP id up7so3001177pbc.15 for ; Fri, 10 May 2013 12:29:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type :content-transfer-encoding:x-gm-message-state; bh=E/wIupdFAQc4Q/Yf6WO/g//PRjll7ZwZCz1gKc7/rjk=; b=CsuR85L1Cn9tdYjFeJn2i0O6SQC4cp6oW2nm3RuWDb5+JLC+MSjDFCTVVNqLA6Ck4l G7Vx42ccK2wvNFLwL0/7Jc3+1mIOgLEWIIg4tidlnypLQ8X1krSb47gzNJkic04DRXOA AaQorb2UEqLY2YEq5n1wTmwqhnYic8F5wneEgzWzewM0+cNJdmDyhCEFLcYh7Y/X0Lyo Hk+p03OzYyPATGzdmCsNdc1bgiAjc7Y2RMayQMPHnWB5X8qtEo7HAkARQKakWPJSrKaT PDsbttIp0yr71DBKH+9XOSYxkAL4qVrn0m5Oi6nssuC12BxBK6G6QKry7HLed1HnajZF pFNQ== X-Received: by 10.66.246.131 with SMTP id xw3mr18958951pac.114.1368214173691; Fri, 10 May 2013 12:29:33 -0700 (PDT) Received: from nehalam.linuxnetplumber.net (static-50-53-71-109.bvtn.or.frontiernet.net. [50.53.71.109]) by mx.google.com with ESMTPSA id nt2sm3724215pbc.17.2013.05.10.12.29.32 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 10 May 2013 12:29:33 -0700 (PDT) Date: Fri, 10 May 2013 12:29:29 -0700 From: Stephen Hemminger To: Bhavesh Davda Message-ID: <20130510122929.0ff687aa@nehalam.linuxnetplumber.net> In-Reply-To: <69354296.5541435.1368213042137.JavaMail.root@vmware.com> References: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> <20130510091549.3c064df6@nehalam.linuxnetplumber.net> <525534677.5312512.1368202896189.JavaMail.root@vmware.com> <20130510114450.7104c5d2@nehalam.linuxnetplumber.net> <69354296.5541435.1368213042137.JavaMail.root@vmware.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnocI/voi70PoItucvDcnkfN/ojAhlncNGuRycRgYJt6CxRYwkq7jGEWSQd3NlvPiwPdpYF Cc: Henry Wang , dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 19:29:33 -0000 On Fri, 10 May 2013 12:10:42 -0700 (PDT) Bhavesh Davda wrote: > Hi Stephen, > > I checked both our hypervisor code and with the experts who wrote and maintain the code, and we don't have any such limitation about not supporting SR-IOV if the motherboard or device doesn't support PCIe ASPM. > > If you can point me to the Intel person(s) who gave you that information (offline, no need to make this public :)), we can make sure such FUD doesn't continue getting spread too far. > > Thanks for making us aware of this FUD though. > > -- > Bhavesh Davda > According to Intel the problem was that the BIOS did not support _OSC table. SR-IOV needs VT-d enabled and BIOS with _OSC and DMA ACPI tables. The _OSC table is an ACPI control method that the kernel uses to interact with PCIe Active Statep Power Management. Linux just assume no ASPM if table is missing, VMWare ESX 5.1 seems to need it. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) by dpdk.org (Postfix) with ESMTP id 7223D6AA8 for ; Fri, 10 May 2013 23:00:00 +0200 (CEST) Received: from sc9-mailhost1.vmware.com (sc9-mailhost1.vmware.com [10.113.161.71]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 77C9A286CD; Fri, 10 May 2013 14:00:00 -0700 (PDT) Received: from zcs-prod-mta-3.vmware.com (zcs-prod-mta-3.vmware.com [10.113.163.65]) by sc9-mailhost1.vmware.com (Postfix) with ESMTP id 724F01870C; Fri, 10 May 2013 14:00:00 -0700 (PDT) Received: from zcs-prod-mta-3.vmware.com (localhost.localdomain [127.0.0.1]) by zcs-prod-mta-3.vmware.com (Postfix) with ESMTP id 58B99E005F; Fri, 10 May 2013 14:00:00 -0700 (PDT) Received: from zcs-prod-mbox-7.vmware.com (lbv-sc9-t2prod2-int.vmware.com [10.113.160.246]) by zcs-prod-mta-3.vmware.com (Postfix) with ESMTP; Fri, 10 May 2013 14:00:00 -0700 (PDT) Date: Fri, 10 May 2013 14:00:00 -0700 (PDT) From: Bhavesh Davda To: Stephen Hemminger Message-ID: <1681866850.5680257.1368219600105.JavaMail.root@vmware.com> In-Reply-To: <20130510122929.0ff687aa@nehalam.linuxnetplumber.net> References: <1676591087.5291867.1368201908283.JavaMail.root@vmware.com> <20130510091549.3c064df6@nehalam.linuxnetplumber.net> <525534677.5312512.1368202896189.JavaMail.root@vmware.com> <20130510114450.7104c5d2@nehalam.linuxnetplumber.net> <69354296.5541435.1368213042137.JavaMail.root@vmware.com> <20130510122929.0ff687aa@nehalam.linuxnetplumber.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.113.163.67] X-Mailer: Zimbra 8.0.3_GA_5664 (ZimbraWebClient - GC26 (Mac)/8.0.3_GA_5664) Thread-Topic: rte_eth_dev_count() returns 0 Thread-Index: WnDVftHuN2D5mrmyyTuCVCrIHw5cSQ== Cc: Henry Wang , dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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, 10 May 2013 21:00:01 -0000 > From: "Stephen Hemminger" > Sent: Friday, May 10, 2013 12:29:29 PM > > On Fri, 10 May 2013 12:10:42 -0700 (PDT) > Bhavesh Davda wrote: > > > Hi Stephen, > > > > I checked both our hypervisor code and with the experts who wrote and > > maintain the code, and we don't have any such limitation about not > > supporting SR-IOV if the motherboard or device doesn't support PCIe ASPM. > > > > If you can point me to the Intel person(s) who gave you that information > > (offline, no need to make this public :)), we can make sure such FUD > > doesn't continue getting spread too far. > > > > Thanks for making us aware of this FUD though. > > > > -- > > Bhavesh Davda > > > > According to Intel the problem was that the BIOS did not support _OSC table. > SR-IOV needs VT-d enabled and BIOS with _OSC and DMA ACPI tables. > The _OSC table is an ACPI control method that the kernel uses to interact > with PCIe Active Statep Power Management. Linux just assume no ASPM if table > is missing, VMWare ESX 5.1 seems to need it > Once again, both in looking at our ACPI _OSC code in the hypervisor and in consulting with the experts, there is no such limitation for SR-IOV support in ESXi. Regards - Bhavesh From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by dpdk.org (Postfix) with ESMTP id 8AC48684A for ; Sat, 18 May 2013 02:10:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12795; q=dns/txt; s=iport; t=1368835805; x=1370045405; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=uBFkf1VGvuUiKjHdfarIlPfuvseRfvO1JuTB0fJle5A=; b=CmE5esJu2AlSjExmqoJHtZyHUKNPao3KW60mB0zGD7m1HTtxI2lX3Kxm 4EU247go739UYQMC6pFR406/+zDC5fntCBvJrXa9qLeOHfiZ++anwVBrZ AqLKgheLjg7BoD8r3C5maYOtvAPv+eYUtY8tq40uJO/loSPHkOwguM+IS U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ag0FAJrGllGtJV2Y/2dsb2JhbABbgkREMMFPgQQWdIIfAQEBAgItTBACAQgRBAEBCx0HMhQDBggCBA4FCIgEDL12jW+BAQ8iBgEGgm1hA6FThyWDD4FxNQ X-IronPort-AV: E=Sophos;i="4.87,695,1363132800"; d="scan'208,217";a="211971166" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 18 May 2013 00:09:48 +0000 Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4I09lg2002193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 18 May 2013 00:09:48 GMT Received: from xmb-aln-x05.cisco.com ([169.254.11.52]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Fri, 17 May 2013 19:09:47 -0500 From: "Rui Vaz (ruvaz)" To: Henry Wang Thread-Topic: [dpdk-dev] rte_eth_dev_count() returns 0 Thread-Index: AQHOTRxLRMe9+1+RZ0K2PTR5yAogVJkKHTrg Date: Sat, 18 May 2013 00:09:46 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.154.212.55] Content-Type: multipart/alternative; boundary="_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2F367xmbalnx05ciscoc_" MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 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: Sat, 18 May 2013 00:10:02 -0000 --_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2F367xmbalnx05ciscoc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Henry, Thank you very much for your help. I have a I350 chipset based NIC, can you tell me why I will not be able to = run l2fwd or l3fwd successfully with SR-IOV enabled in ESXi? Thank you, Rui From: Henry Wang [mailto:wang_hr@neusoft.com] Sent: Thursday, May 09, 2013 6:18 PM To: Rui Vaz (ruvaz) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 As far as I known, DPDK(1.2.3) only supports the following NICs: (1) Intel 82576, 82580, I350 chipset based NICs; (2) Intel 82599, X540T, X520T chipset based NICs; (3) virtual NICs generated by SR-IOV from (2). If the NICs on your C220 M3 is one of (2), you can run l2fwdvf OR l3fwdvf s= uccessfully with SR-IOV enabled in ESXi. And I do not know wheather ESXi 5.0 VMM has SR-IOV function or not. Further more, please reference to DPDK release notes. http://www.intel.com/content/dam/www/public/us/en/documents/release-notes/i= ntel-dpdk-release-notes.pdf On Fri, May 10, 2013 at 9:00 AM, Rui Vaz (ruvaz) > wrote: Hi dev-dpdk, I am following a Intel DPDK Step by Step Instruction found here: http://www= .slideshare.net/hisaki/intel-dpdk-step-by-step-instructions My Hello app from the DPDK examples runs fine, but I get the following erro= r when running the l2fwd app: "EAL: Error - exiting with code: 1 Cause: no Ethernet ports - bye" The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Virtual Mac= hine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon E5-260= 0. I would really appreciate If you could provide some help to solve this issu= e. Thank you, Rui ---------------------------------------------------------------------------= ------------------------ Confidentiality Notice: The information contained in this e-mail and any ac= companying attachment(s) is intended only for the use of the intended recipient and may be confident= ial and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader = of this communication is not the intended recipient, unauthorized use, forwarding, printing, storin= g, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this commu= nication in error,please immediately notify the sender by return e-mail, and delete the original mes= sage and all copies from your system. Thank you. ---------------------------------------------------------------------------= ------------------------ --_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2F367xmbalnx05ciscoc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Henry,

 <= /p>

Thank you very much for y= our help.

 <= /p>

I have a I350 chipset bas= ed NIC, can you tell me why I will not be able to run l2fwd or l3fwd succes= sfully with SR-IOV enabled in ESXi?

 <= /p>

Thank you,

Rui

 <= /p>

From: Henry Wa= ng [mailto:wang_hr@neusoft.com]
Sent: Thursday, May 09, 2013 6:18 PM
To: Rui Vaz (ruvaz)
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0

 

As far as I known, DPDK(1.2.3) only supports the following NI= Cs:

(1) Intel 82576, 82580, I350 chipset based NICs;

(2) Intel 82599, X540T, X520T chipset based NICs;<= /span>

(3) virtual NICs generated by SR-IOV from (2).

 

If the NICs on your C220 M3 is one of (2), you can run l2fwdv= f OR l3fwdvf successfully with SR-IOV enabled in ESXi.

And I do not know wheather ESXi 5.0 VMM has SR-IOV function o= r not.

 

Further more, please reference to DPDK release notes.

 

 

On Fri, May 10, 2013 at 9:00 AM, Rui Vaz (ruvaz) <= ;ruvaz@cisco.com&g= t; wrote:

Hi dev-dpdk,

 

I am following a Intel DPDK Step by Step Instruction found here: http://www.slideshare.net/hisaki/intel-dpdk-step-by-step-instructions

My Hello app from the DPDK examples runs fine, but I get the follo= wing error when running the l2fwd app:

 

“EAL: Error – exiting with code: 1

Cause: no Ethernet ports – bye”

 

The rte_eth_dev_count() call returns 0, I am using a CentOS 6.3 Vi= rtual Machine on VMWare esxi 5.0 on a Cisco UCS C220 M3 which comes with Xeon E5-2600.  

 

I would really appreciate If you could provide some help to solve = this issue.

 

Thank you,

Rui

 

 

------------------------------------------------------------------------= ---------------------------
Confidentiality Notice: The information contained in this e-mail and any ac= companying attachment(s)
is intended only for the use of the intended recipient and may be confident= ial and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader = of this communication is
not the intended recipient, unauthorized use, forwarding, printing,  s= toring, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this commu= nication in error,please
immediately notify the sender by return e-mail, and delete the original mes= sage and all copies from
your system. Thank you.
---------------------------------------------------------------------------= ------------------------

--_000_AFCFCEB8EB0E24448E4EB95988BA1E531FA2F367xmbalnx05ciscoc_--