DPDK usage discussions
 help / color / mirror / Atom feed
From: Shyam Shrivastav <shrivastav.shyam@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Unable to bind intel NIC 82599ES to vfio-pci, uio_pci_generic
Date: Wed, 8 Feb 2017 12:49:28 +0530	[thread overview]
Message-ID: <CAGSp03m=+YPz-fkknCbhLSCNiDPTiqmG0_SgvvAV1TCXVVwnhw@mail.gmail.com> (raw)

Hi All

I am not able to bind 82599 to either uio_pci_generic or vfio-pci
successfully. Any help greatly appreciated, I am completely stuck at this
initial step.

*1) uio_pci_generic* : tools/dpdk-devbind.py script reports success but it
is not detected by EAL on initialisation, still ixgbe driver is detected.
here is relevant console output

[root@unassigned dpdk-16.11]# tools/dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================
0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
drv=uio_pci_generic unused=ixgbe,vfio-pci
0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
drv=uio_pci_generic unused=ixgbe,vfio-pci

[root@unassigned dpdk-16.11]# examples/l2fwd/build/l2fwd  -c f -n 2 p ffff
EAL: Detected 8 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:01:00.0 on NUMA socket -1
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:01:00.1 on NUMA socket -1
EAL:   probe driver: 8086:10fb net_ixgbe
EAL: PCI device 0000:02:00.0 on NUMA socket -1
EAL:   probe driver: 8086:1533 net_e1000_igb
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:1533 net_e1000_igb
MAC updating enabled
Skipping disabled port 0
Skipping disabled port 1
EAL: Error - exiting with code: 1
  Cause: All available ports are disabled. Please set portmask.



*2) vfio-pci :* Configured vfio permissions using setup.sh, bind script
reports error in this case as under

[root@unassigned dpdk-16.11]# tools/dpdk-devbind.py --force -b vfio-pci
01:00.0 01:00.1
Error: bind failed for 0000:01:00.0 - Cannot bind to driver vfio-pci
Error: bind failed for 0000:01:00.1 - Cannot bind to driver vfio-pci

Here is relevant configuration for this to work

[root@unassigned dpdk-16.11]# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.10.0-514.6.1.el7.x86_64
root=UUID=814b781b-1955-4b34-81d6-5c5360325c2e ro crashkernel=auto rhgb
quiet intel_iommu=on iommu=pt
[root@unassigned dpdk-16.11]# dmesg|grep IOMMU
[    0.000000] DMAR: IOMMU enabled
[    0.027925] DMAR-IR: IOAPIC id 2 under DRHD base  0xfed90000 IOMMU 0
[root@unassigned dpdk-16.11]# ulimit -l
unlimited
[root@unassigned dpdk-16.11]# lsmod|grep pci
vfio_pci               37039  0
vfio                   26136  2 vfio_iommu_type1,vfio_pci
irqbypass              13503  2 kvm,vfio_pci
uio_pci_generic        12588  0
uio                    19259  1 uio_pci_generic


Thanks
Shyam

             reply	other threads:[~2017-02-08  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08  7:19 Shyam Shrivastav [this message]
2017-02-13 17:01 ` Ferruh Yigit
2017-02-14  5:34   ` Shyam Shrivastav
2017-02-08 12:47 Shyam Shrivastav

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='CAGSp03m=+YPz-fkknCbhLSCNiDPTiqmG0_SgvvAV1TCXVVwnhw@mail.gmail.com' \
    --to=shrivastav.shyam@gmail.com \
    --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).