From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by dpdk.org (Postfix) with ESMTP id 6F092B367 for ; Mon, 4 Aug 2014 22:24:13 +0200 (CEST) Received: from BL2PR05MB113.namprd05.prod.outlook.com (10.255.232.20) by BL2PR05MB116.namprd05.prod.outlook.com (10.255.232.28) with Microsoft SMTP Server (TLS) id 15.0.995.14; Mon, 4 Aug 2014 20:26:27 +0000 Received: from BL2PR05MB113.namprd05.prod.outlook.com ([169.254.1.253]) by BL2PR05MB113.namprd05.prod.outlook.com ([169.254.1.4]) with mapi id 15.00.0995.014; Mon, 4 Aug 2014 20:26:27 +0000 From: Anjali Kulkarni To: Anjali Kulkarni , "Richardson, Bruce" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Question on using SR-IOV with dpdk apps Thread-Index: AQHPsCJeUSjpLEQ42U+wY3VofjJpeg== Date: Mon, 4 Aug 2014 20:26:27 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [66.129.239.14] x-microsoft-antispam: BCL:0;PCL:0;RULEID: x-forefront-prvs: 0293D40691 x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(13464003)(189002)(199002)(24454002)(51704005)(479174003)(377454003)(79102001)(83506001)(36756003)(31966008)(74662001)(74502001)(86362001)(101416001)(76482001)(64706001)(20776003)(77096002)(77982001)(85306004)(95666004)(99286002)(106356001)(21056001)(105586002)(106116001)(107886001)(107046002)(92726001)(92566001)(85806002)(85852003)(87936001)(4396001)(83072002)(2656002)(1941001)(80022001)(19580395003)(66066001)(81342001)(50986999)(19580405001)(81542001)(83322001)(99396002)(54356999)(46102001); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR05MB116; H:BL2PR05MB113.namprd05.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; LANG:en; Content-Type: text/plain; charset="iso-2022-jp" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps 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: Mon, 04 Aug 2014 20:24:14 -0000 The 4 devices in qs are at 04:10.0, 04:10.1, 04:10.2, 04:10.3 Anjali On 8/4/14 1:24 PM, "Anjali Kulkarni" wrote: >It seems to have detected all 4. But I do see a MAC address not valid: >=1B$B!D=1B(B >=1B$B!D=1B(B >(scrolled up) > >EAL: PCI device 0000:04:10.1 on NUMA socket 0 =1B$B("= =1B(B >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd =1B$B("= =1B(B >EAL: PCI memory mapped at 0x7fd39743e000 =1B$B("= =1B(B >EAL: PCI memory mapped at 0x7fd39743a000 =1B$B("= =1B(B >PMD: The MAC address is not valid. =1B$B("= =1B(B > The most likely cause of this error is that the VM host =1B$B("=1B(B > has not assigned a valid MAC address to this VF device. =1B$B("=1B(B > Please consult the DPDK Release Notes (FAQ section) for =1B$B("=1B(B > a possible solution to this problem. =1B$B("=1B(B >EAL: PCI device 0000:04:10.2 on NUMA socket 0 =1B$B("= =1B(B >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd =1B$B("= =1B(B >EAL: PCI memory mapped at 0x7fd397436000 =1B$B("= =1B(B >EAL: PCI memory mapped at 0x7fd397432000 =1B$B("= =1B(B >EAL: PCI device 0000:04:10.3 on NUMA socket 0 =1B$B("= =1B(B >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd =1B$B("= =1B(B >EAL: PCI memory mapped at 0x7fd39742e000 =1B$B("= =1B(B >EAL: PCI memory mapped at 0x7fd39742a000 =1B$B("= =1B(B >PMD: The MAC address is not valid. =1B$B("= =1B(B > The most likely cause of this error is that the VM host =1B$B("=1B(B > has not assigned a valid MAC address to this VF device. =1B$B("=1B(B > Please consult the DPDK Release Notes (FAQ section) for =1B$B("=1B(B > a possible solution to this problem. > > > >On 8/4/14 12:53 PM, "Richardson, Bruce" >wrote: > >> >>> -----Original Message----- >>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anjali Kulkarni >>> Sent: Monday, August 04, 2014 12:45 PM >>> To: dev@dpdk.org >>> Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps >>>=20 >>> Forgot to clarify, this is a specialized app, and the first parameter >>>of >>> each () is the dpdk port no. >>>=20 >>> On 8/4/14 12:43 PM, "Anjali Kulkarni" wrote: >>>=20 >>> >Hi, >>> > >>> >I am using SR-IOV and pass through to run a DPDK app. I am running it >>>on >>> >host. SR-IOV should split the NIC into multiple Vfs. I have split each >>>NIC >>> >into 2 Vfs. However, when I run the DPDK app, I get error initializing >>>the >>> >port no.2 of DPDK. >>> >I am running the app with these options: >>> >--rx "(0,0,0,1),(1,0,2,1), (2,0,3,1), (3,0,4,1)" --tx "(0,1), (1,1), >>> >(2,1), (3,1)" >>> > >>> >This is for 2 physical NICs, each having 2 Vfs. The error I get is: >>> > >>> >Initializing NIC port 0 ... | >>> >|RPIOIF DETACHED >>> >|Initializing NIC port 0 RX queue 0 ... | >>> >| >>> >|Initializing NIC port 0 TX queue 0 ... | >>> >|HOSTIF DETACHED >>> >|Initializing NIC port 1 ... | >>> >| >>> >|Initializing NIC port 1 RX queue 0 ... | >>> >| >>> >|Initializing NIC port 1 TX queue 0 ... | >>> >| >>> >|Initializing NIC port 2 ... | >>> >| >>> >|PANIC in app_init_nics(): | >>> >| >>> >|Cannot init NIC port 2 (-22) >>> > >>> > >>> >Can someone pls clarify how DPDK views it's port nos, i.e. Scans the >>> >devices and sees each nic? I see 4 /dev/uioX devices. I assume it >>>scans >>> >for these igb_uio devices. These are present. Then why can it not >>>detect >>> >the other 2 NICs? >>> > >>> >Thanks >>> >Anjali >>> > >> >>Hi, >> >>For debugging issues with PCI devices not being found, can you please >>include the output from the EAL on startup, especially any messages >>concerning the PCI bus scan being done. >> >>Regards, >>/Bruce >