* Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
@ 2014-08-04 20:26 Anjali Kulkarni
2014-08-05 14:38 ` Patrick McGleenon
0 siblings, 1 reply; 7+ messages in thread
From: Anjali Kulkarni @ 2014-08-04 20:26 UTC (permalink / raw)
To: Anjali Kulkarni, Richardson, Bruce, 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" <anjali@juniper.net> wrote:
>It seems to have detected all 4. But I do see a MAC address not valid:
>…
>…
>(scrolled up)
>
>EAL: PCI device 0000:04:10.1 on NUMA socket 0 │
>EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
>EAL: PCI memory mapped at 0x7fd39743e000 │
>EAL: PCI memory mapped at 0x7fd39743a000 │
>PMD: The MAC address is not valid. │
> The most likely cause of this error is that the VM host │
> has not assigned a valid MAC address to this VF device. │
> Please consult the DPDK Release Notes (FAQ section) for │
> a possible solution to this problem. │
>EAL: PCI device 0000:04:10.2 on NUMA socket 0 │
>EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
>EAL: PCI memory mapped at 0x7fd397436000 │
>EAL: PCI memory mapped at 0x7fd397432000 │
>EAL: PCI device 0000:04:10.3 on NUMA socket 0 │
>EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
>EAL: PCI memory mapped at 0x7fd39742e000 │
>EAL: PCI memory mapped at 0x7fd39742a000 │
>PMD: The MAC address is not valid. │
> The most likely cause of this error is that the VM host │
> has not assigned a valid MAC address to this VF device. │
> Please consult the DPDK Release Notes (FAQ section) for │
> a possible solution to this problem.
>
>
>
>On 8/4/14 12:53 PM, "Richardson, Bruce" <bruce.richardson@intel.com>
>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
>>>
>>> Forgot to clarify, this is a specialized app, and the first parameter
>>>of
>>> each () is the dpdk port no.
>>>
>>> On 8/4/14 12:43 PM, "Anjali Kulkarni" <anjali@juniper.net> wrote:
>>>
>>> >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
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
2014-08-04 20:26 [dpdk-dev] Question on using SR-IOV with dpdk apps Anjali Kulkarni
@ 2014-08-05 14:38 ` Patrick McGleenon
2014-08-05 15:09 ` Xie, Huawei
0 siblings, 1 reply; 7+ messages in thread
From: Patrick McGleenon @ 2014-08-05 14:38 UTC (permalink / raw)
To: Anjali Kulkarni, Richardson, Bruce, dev
I had this when the PF was down, bringing it back with "ifup" fixed it. Assuming you've already checked it's not the issue described in the FAQ :)
With a RHEL 6.5 host the ixgbe driver prints the VF MAC addresses in /var/log/syslog when the VFs are enabled
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anjali Kulkarni
Sent: 04 August 2014 21:26
To: Anjali Kulkarni; Richardson, Bruce; dev@dpdk.org
Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
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" <anjali@juniper.net> wrote:
>It seems to have detected all 4. But I do see a MAC address not valid:
>:
>:
>(scrolled up)
>
>EAL: PCI device 0000:04:10.1 on NUMA socket 0 │
>EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
>EAL: PCI memory mapped at 0x7fd39743e000 │
>EAL: PCI memory mapped at 0x7fd39743a000 │
>PMD: The MAC address is not valid. │
> The most likely cause of this error is that the VM host │
> has not assigned a valid MAC address to this VF device. │
> Please consult the DPDK Release Notes (FAQ section) for │
> a possible solution to this problem. │
>EAL: PCI device 0000:04:10.2 on NUMA socket 0 │
>EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
>EAL: PCI memory mapped at 0x7fd397436000 │
>EAL: PCI memory mapped at 0x7fd397432000 │
>EAL: PCI device 0000:04:10.3 on NUMA socket 0 │
>EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
>EAL: PCI memory mapped at 0x7fd39742e000 │
>EAL: PCI memory mapped at 0x7fd39742a000 │
>PMD: The MAC address is not valid. │
> The most likely cause of this error is that the VM host │
> has not assigned a valid MAC address to this VF device. │
> Please consult the DPDK Release Notes (FAQ section) for │
> a possible solution to this problem.
>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
2014-08-05 14:38 ` Patrick McGleenon
@ 2014-08-05 15:09 ` Xie, Huawei
0 siblings, 0 replies; 7+ messages in thread
From: Xie, Huawei @ 2014-08-05 15:09 UTC (permalink / raw)
To: Patrick McGleenon, Anjali Kulkarni, Richardson, Bruce, dev
Since some version of ixgbe driver, it will not generate mac address for the VFs. You could use ip link set to set mac address for the VFs.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Patrick McGleenon
> Sent: Tuesday, August 05, 2014 10:39 PM
> To: Anjali Kulkarni; Richardson, Bruce; dev@dpdk.org
> Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
>
> I had this when the PF was down, bringing it back with "ifup" fixed it. Assuming
> you've already checked it's not the issue described in the FAQ :)
> With a RHEL 6.5 host the ixgbe driver prints the VF MAC addresses in
> /var/log/syslog when the VFs are enabled
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Anjali Kulkarni
> Sent: 04 August 2014 21:26
> To: Anjali Kulkarni; Richardson, Bruce; dev@dpdk.org
> Subject: Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
>
> 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" <anjali@juniper.net> wrote:
>
> >It seems to have detected all 4. But I do see a MAC address not valid:
> >:
> >:
> >(scrolled up)
> >
> >EAL: PCI device 0000:04:10.1 on NUMA socket 0 │
> >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
> >EAL: PCI memory mapped at 0x7fd39743e000 │
> >EAL: PCI memory mapped at 0x7fd39743a000 │
> >PMD: The MAC address is not valid. │
> > The most likely cause of this error is that the VM host │
> > has not assigned a valid MAC address to this VF device. │
> > Please consult the DPDK Release Notes (FAQ section) for │
> > a possible solution to this problem. │
> >EAL: PCI device 0000:04:10.2 on NUMA socket 0 │
> >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
> >EAL: PCI memory mapped at 0x7fd397436000 │
> >EAL: PCI memory mapped at 0x7fd397432000 │
> >EAL: PCI device 0000:04:10.3 on NUMA socket 0 │
> >EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
> >EAL: PCI memory mapped at 0x7fd39742e000 │
> >EAL: PCI memory mapped at 0x7fd39742a000 │
> >PMD: The MAC address is not valid. │
> > The most likely cause of this error is that the VM host │
> > has not assigned a valid MAC address to this VF device. │
> > Please consult the DPDK Release Notes (FAQ section) for │
> > a possible solution to this problem.
> >
> >
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
2014-08-04 19:53 ` Richardson, Bruce
@ 2014-08-04 20:24 ` Anjali Kulkarni
0 siblings, 0 replies; 7+ messages in thread
From: Anjali Kulkarni @ 2014-08-04 20:24 UTC (permalink / raw)
To: Richardson, Bruce, dev
It seems to have detected all 4. But I do see a MAC address not valid:
…
…
(scrolled up)
EAL: PCI device 0000:04:10.1 on NUMA socket 0 │
EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
EAL: PCI memory mapped at 0x7fd39743e000 │
EAL: PCI memory mapped at 0x7fd39743a000 │
PMD: The MAC address is not valid. │
The most likely cause of this error is that the VM host │
has not assigned a valid MAC address to this VF device. │
Please consult the DPDK Release Notes (FAQ section) for │
a possible solution to this problem. │
EAL: PCI device 0000:04:10.2 on NUMA socket 0 │
EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
EAL: PCI memory mapped at 0x7fd397436000 │
EAL: PCI memory mapped at 0x7fd397432000 │
EAL: PCI device 0000:04:10.3 on NUMA socket 0 │
EAL: probe driver: 8086:10ed rte_ixgbevf_pmd │
EAL: PCI memory mapped at 0x7fd39742e000 │
EAL: PCI memory mapped at 0x7fd39742a000 │
PMD: The MAC address is not valid. │
The most likely cause of this error is that the VM host │
has not assigned a valid MAC address to this VF device. │
Please consult the DPDK Release Notes (FAQ section) for │
a possible solution to this problem.
On 8/4/14 12:53 PM, "Richardson, Bruce" <bruce.richardson@intel.com> 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
>>
>> Forgot to clarify, this is a specialized app, and the first parameter of
>> each () is the dpdk port no.
>>
>> On 8/4/14 12:43 PM, "Anjali Kulkarni" <anjali@juniper.net> wrote:
>>
>> >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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
2014-08-04 19:44 ` Anjali Kulkarni
@ 2014-08-04 19:53 ` Richardson, Bruce
2014-08-04 20:24 ` Anjali Kulkarni
0 siblings, 1 reply; 7+ messages in thread
From: Richardson, Bruce @ 2014-08-04 19:53 UTC (permalink / raw)
To: Anjali Kulkarni, dev
> -----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
>
> Forgot to clarify, this is a specialized app, and the first parameter of
> each () is the dpdk port no.
>
> On 8/4/14 12:43 PM, "Anjali Kulkarni" <anjali@juniper.net> wrote:
>
> >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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-dev] Question on using SR-IOV with dpdk apps
2014-08-04 19:43 Anjali Kulkarni
@ 2014-08-04 19:44 ` Anjali Kulkarni
2014-08-04 19:53 ` Richardson, Bruce
0 siblings, 1 reply; 7+ messages in thread
From: Anjali Kulkarni @ 2014-08-04 19:44 UTC (permalink / raw)
To: dev
Forgot to clarify, this is a specialized app, and the first parameter of
each () is the dpdk port no.
On 8/4/14 12:43 PM, "Anjali Kulkarni" <anjali@juniper.net> wrote:
>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
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [dpdk-dev] Question on using SR-IOV with dpdk apps
@ 2014-08-04 19:43 Anjali Kulkarni
2014-08-04 19:44 ` Anjali Kulkarni
0 siblings, 1 reply; 7+ messages in thread
From: Anjali Kulkarni @ 2014-08-04 19:43 UTC (permalink / raw)
To: dev
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-08-05 15:07 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-04 20:26 [dpdk-dev] Question on using SR-IOV with dpdk apps Anjali Kulkarni
2014-08-05 14:38 ` Patrick McGleenon
2014-08-05 15:09 ` Xie, Huawei
-- strict thread matches above, loose matches on Subject: below --
2014-08-04 19:43 Anjali Kulkarni
2014-08-04 19:44 ` Anjali Kulkarni
2014-08-04 19:53 ` Richardson, Bruce
2014-08-04 20:24 ` Anjali Kulkarni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).