DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raju-dev grishma <rajugrishma@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK versions and SRIOV on XL710.
Date: Fri, 21 Jul 2017 12:18:23 +0530	[thread overview]
Message-ID: <CAB6=LCtiKgR3TTL4wUbQ5JKQtE-+g6nmTysWg9kWRGSrKwU_xg@mail.gmail.com> (raw)

Hi I have a host and XL710 nic cards and created few VFs on these NIC. I
created two VMs on that host and assign one VF to each VM.

VM#1: It has RHEL 7.2 installed and I use DPDK version 2.2.0

SRIOV ports on this VM works OK. testmpd works.

The SRIOV interfaces comes up with below logs when I invoke testpmd.

EAL:  PCI device 0000:0b:00.0 on NUMA socket -1
EAL:   probe driver: 8086:154c rte_i40evf_pmd
EAL:   PCI memory mapped at 0x7fefdce00000
EAL:   PCI memory mapped at 0x7fefdce10000


VM#2: It has Ubuntu 16.04.2 and I use DPDK 17.05
SRIOV ports don't show up when I invoke testpmd.

EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:154c net_i40e_vf
i40evf_init_vf(): init_adminq failed
i40evf_dev_init(): Init vf failed
EAL: Requested device 0000:03:00.0 cannot be used

I see one difference here. For the same NIC beneath, the DPDK picks
different driver on this VM. (net_i40e_vf as compared to rte_i40evf_pmd).
As I understand the dpdk.h file has this switching based on RTE version.

Question is why it fails on this VM that has different (later version) of
dpdk ?
Is there any settings I need to do on the guest OS (Ubuntu ) on VM#2?
could it be the NIC firmware that might be incompatible with driver used by
dpdk on VM#2?

Any pointers to move on ?

Thanks
Raju

                 reply	other threads:[~2017-07-21  6:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAB6=LCtiKgR3TTL4wUbQ5JKQtE-+g6nmTysWg9kWRGSrKwU_xg@mail.gmail.com' \
    --to=rajugrishma@gmail.com \
    --cc=dev@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).