From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anjali Kulkarni Subject: Re: Question on using SR-IOV with dpdk apps Date: Mon, 4 Aug 2014 20:26:27 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable To: Anjali Kulkarni , "Richardson, Bruce" , "dev-VfR2kkLFssw@public.gmane.org" Return-path: Content-Language: en-US Content-ID: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 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-VfR2kkLFssw@public.gmane.org] On Behalf Of Anjali Kulkarni >>> Sent: Monday, August 04, 2014 12:45 PM >>> To: dev-VfR2kkLFssw@public.gmane.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 >