From: Anjali Kulkarni <anjali-3r7Miqu9kMnR7s880joybQ@public.gmane.org>
To: "Richardson,
Bruce" <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"dev-VfR2kkLFssw@public.gmane.org"
<dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Question on using SR-IOV with dpdk apps
Date: Mon, 4 Aug 2014 20:24:58 +0000 [thread overview]
Message-ID: <D0053935.2D3B7%anjali@juniper.net> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B0343D4EE6-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> 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
>>
>> 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-3r7Miqu9kMnR7s880joybQ@public.gmane.org> 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
next prev parent reply other threads:[~2014-08-04 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 19:43 Question on using SR-IOV with dpdk apps Anjali Kulkarni
[not found] ` <D0052E56.2D38F%anjali-3r7Miqu9kMnR7s880joybQ@public.gmane.org>
2014-08-04 19:44 ` Anjali Kulkarni
[not found] ` <D005309D.2D3AA%anjali-3r7Miqu9kMnR7s880joybQ@public.gmane.org>
2014-08-04 19:53 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B0343D4EE6-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-04 20:24 ` Anjali Kulkarni [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-04 20:26 Anjali Kulkarni
[not found] ` <D0053A5F.2D3C5%anjali-3r7Miqu9kMnR7s880joybQ@public.gmane.org>
2014-08-05 14:38 ` Patrick McGleenon
[not found] ` <78e1ff3841f6401c828eab452ea8b4f1-3XF1nH8AwqXxT4Sa17bWpJLWcSx1hRipwIZJ9u9yWa8oOQlpcoRfSA@public.gmane.org>
2014-08-05 15:09 ` Xie, Huawei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D0053935.2D3B7%anjali@juniper.net \
--to=anjali-3r7miqu9kmnr7s880joybq@public.gmane.org \
--cc=bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.