DPDK usage discussions
 help / color / mirror / Atom feed
From: Deepak Gowda <deepak.dt06@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, users@dpdk.org
Subject: Re: [dpdk-users] [dpdk-dev] SR-IOV with vfio-pci
Date: Thu, 26 Sep 2019 16:32:25 +0530	[thread overview]
Message-ID: <CAM84qfrbrPQARzD8kZ8gxYiAAS2D_=XrLeSonQdWetYshU01ZA@mail.gmail.com> (raw)
In-Reply-To: <20190926083602.GC1821@bricha3-MOBL.ger.corp.intel.com>

Hi Bruce,

Thank you for the quick response.
No it didn't work with igb_uio either.
The reason is,

I had made a mistake,
When i created VFs on top of the 10G card, that interface was down
actually. but i proceeded anyway because i could see mac on these vfs from
"ifconfig -a".
After a bit of looking around, i found that eth_ixgbevf_dev_init() expects
these VFs to have some mac. Then i looked again with "ip link show dev
parent_if_name", these vfs had no mac.
So i administratively up'ed(ifconfig up) the parent interface and then
created VFs on top it and bound them to vfio-pci. Now the test-pmd app
works fine.
Sorry for the false alarm.


Thanks so much,
-DG







On Thu, 26 Sep 2019 at 14:06, Bruce Richardson <bruce.richardson@intel.com>
wrote:

> On Thu, Sep 26, 2019 at 11:57:04AM +0530, Deepak Gowda wrote:
> > Hi,
> >
> > I'm trying to run test-pmd application with virtual functions bound to
> > vfio-pci.
> > I'm able to bind and unbind the virtual functions from ixgbevf to
> vfio-pci
> > and vice-versa
> > And i'm seeing the below VF Initialization failure error, i can't seem to
> > figure out what's going wrong here,
> >
> > EAL:   using IOMMU type 1 (Type 1)
> > PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> > EAL: Releasing pci mapped resource for 0000:04:10.0
> > EAL: Calling pci_unmap_resource for 0000:04:10.0 at 0x7f808ba00000
> > EAL: Calling pci_unmap_resource for 0000:04:10.0 at 0x7f808ba04000
> > EAL: Requested device 0000:04:10.0 cannot be used
> > EAL: PCI device 0000:04:10.2 on NUMA socket 0
> > EAL:   probe driver: 8086:10ed net_ixgbe_vf
> > EAL:   using IOMMU type 1 (Type 1)
> > PMD: eth_ixgbevf_dev_init(): VF Initialization Failure: -15
> > EAL: Releasing pci mapped resource for 0000:04:10.2
> > EAL: Calling pci_unmap_resource for 0000:04:10.2 at 0x7f808ba08000
> > EAL: Calling pci_unmap_resource for 0000:04:10.2 at 0x7f808ba0c000
> > EAL: Requested device 0000:04:10.2 cannot be used
> >
> > Here's some more information:
> > I'm using dpdk-17.11.
> > Created Virtual functions on Intel 82599ES 10G cards.
> > Bound these vfs to vfio-pci.
> > And tried to run the test-pmd.
> >
> >
> Is this a vfio specific problem? Does the app work with those ports if they
> are bound to igb_uio, for instance?
>
> /Bruce
>

      reply	other threads:[~2019-09-26 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM84qfqmFGuwkVQKq4pD5wShjrNMJDrCYyE5YjY2yv88-17sdw@mail.gmail.com>
2019-09-26  8:36 ` Bruce Richardson
2019-09-26 11:02   ` Deepak Gowda [this message]

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='CAM84qfrbrPQARzD8kZ8gxYiAAS2D_=XrLeSonQdWetYshU01ZA@mail.gmail.com' \
    --to=deepak.dt06@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).