DPDK usage discussions
 help / color / mirror / Atom feed
From: Shivaram Mysore <shivaram.mysore@gmail.com>
To: Vincenzo Maffione <v.maffione@gmail.com>
Cc: users@dpdk.org, Giuseppe Lettieri <g.lettieri@iet.unipi.it>
Subject: Re: [dpdk-users] Cannot attach DPDK NIC port to OVS
Date: Thu, 20 Apr 2017 09:13:06 -0700	[thread overview]
Message-ID: <CAJRY+jqQEcfbbbiazDj47ac-OgWzwMVnK+Oh4kgpAm9OZQbV-w@mail.gmail.com> (raw)
In-Reply-To: <CA+_eA9jYG_TioXZYAVXr+DMO3Ft9MqF09DNBuXZ88qS2v13itA@mail.gmail.com>

I have a feeling that vfio-pci is not installed.  Note that you will have
to edit /etc/modules to load on boot.

You can also check by
# lsmod | grep vfio

To load on demand - use
# modprobe vfio-pci



On Thu, Apr 20, 2017 at 9:03 AM, Vincenzo Maffione <v.maffione@gmail.com>
wrote:

> Hi,
>   I installed OVS 2.7.0 and use uio_pci_generic in place of vfio-pci, and
> the error disappeared.
>
> Thanks,
>   Vincenzo
>
> 2017-04-15 17:56 GMT+02:00 Shivaram Mysore <shivaram.mysore@gmail.com>:
>
>> You should look at emails from -(Hint:  search DPDK in subject)
>>
>> https://mail.openvswitch.org/pipermail/ovs-discuss/2017-March/thread.html
>> https://mail.openvswitch.org/pipermail/ovs-discuss/2017-April/thread.html
>> https://mail.openvswitch.org/pipermail/ovs-discuss/2017-April/044155.html
>>
>> If possible, I would recommend using Ubuntu 17.04 with OVS 2.7 with DPDK
>> packages from http://packages.wand.net.nz/ which can simplify your
>> deployment.
>>
>> /Shivaram
>>
>> On Fri, Apr 14, 2017 at 4:04 AM, Vincenzo Maffione <
>> vincenzo.maffione@ing.unipi.it> wrote:
>>
>>> Hi,
>>>   I would like to attach one of my ixgbe NIC ports to an OpenVSwitch
>>> instance, but I keep getting an unexpected error, see below.
>>>
>>> I've successfully bound both my ixgbe NIC ports to DPDK, using VFIO:
>>>
>>> # tools/dpdk-devbind.py --status
>>>
>>> Network devices using DPDK-compatible driver
>>> ============================================
>>> 0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
>>> drv=vfio-pci
>>> unused=ixgbe
>>> 0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
>>> drv=vfio-pci
>>> unused=ixgbe
>>>
>>> Network devices using kernel driver
>>> ===================================
>>> 0000:00:19.0 'Ethernet Connection (2) I218-V' if=eno1 drv=e1000e
>>> unused=vfio-pci
>>> 0000:06:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
>>> if=enp6s0 drv=r8169 unused=vfio-pci
>>> 0000:07:00.0 '82574L Gigabit Network Connection' if=enp7s0 drv=e1000e
>>> unused=vfio-pci
>>>
>>> Other network devices
>>> =====================
>>> <none>
>>>
>>> Crypto devices using DPDK-compatible driver
>>> ===========================================
>>> <none>
>>>
>>> Crypto devices using kernel driver
>>> ==================================
>>> <none>
>>>
>>> Other crypto devices
>>> ====================
>>> <none>
>>>
>>>
>>> Then I created a bridge
>>>
>>> # ovs-vsctl add-br obr1 -- set bridge obr1 datapath_type=netdev
>>>
>>> But then when trying to add the dpdk NIC:
>>>
>>> # ovs-vsctl add-port obr1 dpdk-p0 -- set Interface dpdk-p0 type=dpdk
>>> options:dpdk-devargs=0000:01:00.0
>>>
>>> the command fails, and I get this in the log:
>>>
>>> ovs-vswitchd[353]: 2017-04-14T10:54:06Z|00026|bridge|WARN|could not open
>>> network device dpdk-p0 (No such device)
>>> ovs-vswitchd[353]: ovs|00026|bridge|WARN|could not open network device
>>> dpdk-p0 (No such device)
>>>
>>> Note that I've successfully managed to setup an OVS instance with two
>>> DPDK
>>> vhost-user ports (each one assigned to a QEMU VM): this is why I'm
>>> confident my OVS is built and configured correctly to work with DPDK.
>>> Also,
>>> DPDK by itself is working as expected, I can use dpdk pktgen.
>>> Moreover, OVS log shows that DPDK is recognized
>>>
>>> [...]
>>> ovs|00005|dpdk|INFO|DPDK Enabled, initializing
>>> [...]
>>>
>>> Note that I'm carefully following the documentation here
>>> http://docs.openvswitch.org/en/latest/intro/install/dpdk/ and here
>>> http://docs.openvswitch.org/en/latest/howto/dpdk/
>>>
>>> More info:
>>>
>>> DPDK version: 16.11
>>> OVS version: 2.6.1, configured with --with-dpdk
>>> Host: Archlinux
>>> /proc/cmdline: BOOT_IMAGE=../vmlinuz-linux-vfio
>>> root=UUID=1c777330-3f00-4ab8-8d5d-d4b2b5d860b0 rw intel_iommu=on
>>> hugepages=2048 pci=assign-busses pcie_acs_override=downstream
>>> initrd=../initramfs-linux-vfio.img
>>>
>>> Can anybody help? I'm at a loss here.
>>>
>>> Thanks,
>>>   Vincenzo
>>>
>>
>>
>
>
> --
> Vincenzo Maffione
>

  parent reply	other threads:[~2017-04-20 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 11:04 Vincenzo Maffione
2017-04-15 15:56 ` Shivaram Mysore
     [not found]   ` <CA+_eA9jYG_TioXZYAVXr+DMO3Ft9MqF09DNBuXZ88qS2v13itA@mail.gmail.com>
2017-04-20 16:13     ` Shivaram Mysore [this message]
2017-04-20 16:21       ` Vincenzo Maffione
2017-04-21 10:53         ` Vincenzo Maffione

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=CAJRY+jqQEcfbbbiazDj47ac-OgWzwMVnK+Oh4kgpAm9OZQbV-w@mail.gmail.com \
    --to=shivaram.mysore@gmail.com \
    --cc=g.lettieri@iet.unipi.it \
    --cc=users@dpdk.org \
    --cc=v.maffione@gmail.com \
    /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).