From: "Wiles, Keith" <keith.wiles@intel.com>
To: Sara Gittlin <sara.gittlin@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] pktgen - !PANIC!: *** Did not find any ports to use ***
Date: Tue, 28 May 2019 13:59:48 +0000 [thread overview]
Message-ID: <862B94BB-6438-402F-AE04-60E4EFD00406@intel.com> (raw)
In-Reply-To: <CAA_4wjaFKafCk6pqHWOz7w=ZzqeEa7N-xThnrYRasi6GnSFVvQ@mail.gmail.com>
> On May 28, 2019, at 12:33 AM, Sara Gittlin <sara.gittlin@gmail.com> wrote:
>
> Hello
> According the dpdk release notes - my NIC - Onboard NIC: *Intel(R)
> X552*/X557-AT
> (2x10G) was tested
>
> Tested Platforms
>
> ----------------
>
>
> #. SuperMicro 1U
>
>
> - BIOS: 1.0c
>
> - Processor: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz
>
>
> #. SuperMicro 1U
>
>
> - BIOS: 1.0a
>
> - Processor: Intel(R) Xeon(R) CPU D-1540 @ 2.00GHz
>
> *- Onboard NIC: Intel(R) X552/X557-AT (2x10G)*
>
> Thank you
>
As Stephen stated this normally something to do with device IDs or NICs not bound to the correct module igb_uio, vfio, …, this I believe is a configuration problem and not a Pktgen problem. The pktgen command line looks correct, but DPDK needs to see the ports before pktgen can use them.
I did not see which kernel module you have attached NICs can you show the dpdk-devbind.py -s output or if you forgot to do that bind inside the VM please bind the NICs to the kernel module you are using. Beyond this little help I do not use VMs very often to get pktgen and not much help here, but as I stated this is not a pktgen problem.
Have you tested other DPDK apps like testpmd/l3fwd/l2fwd and do they work?
> -Sara
>
> On Mon, May 27, 2019 at 5:56 PM Sara Gittlin <sara.gittlin@gmail.com> wrote:
>
>> Thank you Stephen
>> i can run pktgen on the host with same 2 VF's
>> Regards
>> -Sara
>>
>>
>> On Mon, May 27, 2019 at 5:52 PM Stephen Hemminger <
>> stephen@networkplumber.org> wrote:
>>
>>> On Mon, 27 May 2019 17:44:17 +0300
>>> Sara Gittlin <sara.gittlin@gmail.com> wrote:
>>>
>>>> Hello ,
>>>> I'm running pktgen on a ubuntu-16.0p4 VM w 3 CPU's,
>>>> I added 2 SRIOV VFs devices to the VM - and i can see them w lspci or
>>>> dpdk-devbind --status
>>>> 00:08.0 Ethernet controller: Intel Corporation Ethernet Connection X552
>>>> Virtual Function
>>>> 00:09.0 Ethernet controller: Intel Corporation Ethernet Connection X552
>>>> Virtual Function
>>>
>>> Most likely these devices are missing/not supported by DPDK driver.
>>> Look at the numeric id's (lspci -n) and compare them with the list
>>> of pci ids in the driver source.
>>>
>>> In the past with Intel devices it also helped to look at the Linux
>>> kernel driver. Sometimes the missing id's were there and some small
>>> changes to the MAC code was necessary to get them to work.
>>>
>>
Regards,
Keith
next prev parent reply other threads:[~2019-05-28 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 14:44 Sara Gittlin
2019-05-27 14:52 ` Stephen Hemminger
2019-05-27 14:56 ` Sara Gittlin
2019-05-28 5:33 ` Sara Gittlin
2019-05-28 13:59 ` Wiles, Keith [this message]
2019-05-28 14:02 ` Stephen Hemminger
2019-05-28 18:09 ` Sara Gittlin
2019-05-29 8:40 ` [dpdk-users] pktgen Did not find any ports to use Sara Gittlin
2019-05-29 10:30 ` [dpdk-users] pktgen - !PANIC!: *** Did not find any ports to use *** Sara Gittlin
2019-05-29 12:39 ` [dpdk-users] pktgen -**SOLVED** " Sara Gittlin
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=862B94BB-6438-402F-AE04-60E4EFD00406@intel.com \
--to=keith.wiles@intel.com \
--cc=sara.gittlin@gmail.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.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 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).