DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wu, Xiaoban" <Xiaoban_Wu@student.uml.edu>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Mellanox 100G NIC, VF SR-IOV, docker container, EAL could not detect the device
Date: Tue, 23 May 2017 05:39:36 +0000	[thread overview]
Message-ID: <BN6PR02MB2706E8A448466C5F7B98081CBCF90@BN6PR02MB2706.namprd02.prod.outlook.com> (raw)

Dear DPDK users,


I am trying to use the VF of the Mellanox 100G NIC enabled by SR-IOV. The following is what I have done.


     1. Add "intel_iommu=on iommu=pt" to kernel command line option, update-grub, and reboot

     2. Install the MLNX-OFED, reboot

     3. In default the card is in infiband mode, so I switched it to ethernet mode (in order to run DPDK application) and reboot.

     4. mst start

         mlxconfig -d /dev/mst/mt4115_pciconf0 q #query
         mlxconfig -d /dev/mst/mt4115_pciconf0 set SRIOV_EN=1 NUM_OF_VFS=1
         reboot
     5. echo 1 > /sys/bus/pci/devices/0000\:83\:00.0/mlx5_num_vfs
     6. modprobe vfio-pci
     7. dpdk-devbind.py --status
     8. dpdk-devbind.py -b vfio-pci 0000:83:00.1
     9. ls -al /dev/vfio
     10. docker run -it --privileged --device=/dev/vfio/54:/dev/vfio/54 --device=/dev/vfio/vfio:/dev/vfio/vfio -v /mnt/huge/:/dev/hugepages/ -v /var/run:/var/run  $IMAGEID bash
     11. $dpdkapp -c 0x01 --socket-mem=128,128 --file-prefix="docker1"

However, in the EAL part, it does not list any usable devices
EAL: Detected 12 lcore(s)
EAL: Probing VFIO support...
EAL: VFIO support initialized
PMD: bnxt_rte_pmd_init() called for (null)
Error, rte_eth_dev_configure() returns negative!

Can anybody please point out any possible solution? Looking forward to your reply. Thanks very much for your help.

Best wishes,
Xiaoban

             reply	other threads:[~2017-05-23  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  5:39 Wu, Xiaoban [this message]
2017-05-23  8:12 ` Adrien Mazarguil
2017-05-24  1:01   ` Wu, Xiaoban
2017-05-24  7:51     ` Adrien Mazarguil

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=BN6PR02MB2706E8A448466C5F7B98081CBCF90@BN6PR02MB2706.namprd02.prod.outlook.com \
    --to=xiaoban_wu@student.uml.edu \
    --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).