[ovs-discuss] No Ethernet devices found with I350

Rapelly, Varun vrapelly at sonusnet.com
Tue Jun 23 07:23:47 UTC 2015


Hi All,

I'm a newbie to openvswitch and I followed the below link to install ovs with DPDK on RHEL7 machine.

[root at artha ~]# uname -a
Linux BL4 3.10.0-123.el7.x86_64 #1 SMP Mon May 5 11:16:57 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

https://github.com/openvswitch/ovs/blob/master/INSTALL.DPDK.md

When I ran vswitch daemon, it reports following error [I binded igb_uio to the i350 NIC].

2015-06-22T18:04:38Z|00003|dpdk|ERR|No Ethernet devices found. Try assigning ports to UIO.
2015-06-22T18:04:38Z|00004|dpdk|INFO|Ethernet Device Count: 0

Following PCI bind status.

[root at artha ~]# ./dpdk-1.7.1/tools/dpdk_nic_bind.py --status

Network devices using DPDK-compatible driver
============================================
0000:0a:00.0 'I350 Gigabit Network Connection' drv=igb_uio unused=

Network devices using kernel driver
===================================
0000:03:00.0 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno1 drv=tg3 unused=
0000:03:00.1 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno2 drv=tg3 unused=
0000:03:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno3 drv=tg3 unused=
0000:03:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eno4 drv=tg3 unused=
0000:0a:00.1 'I350 Gigabit Network Connection' if=ens3f1 drv=igb unused=

Other network devices
=====================
<none>

Then I created I ovs bridge using below cmd:
./ovs-vsctl --no-wait add-br ovs -- set Bridge ovs datapath_type=netdev
./ovs-vsctl add-port ovs dpdk0 -- set Interface dpdk0 type=dpdk

When I add dpdk port it reports, "could not open network device dpdk0 (Unknown error -19)"

Please let me know

1.  What could be possible reason for not detecting the interface which is binded to igb_uio?

2.  How to add the port which is binded to igb_uio here?

Thanks in advance.

Regards,
Varun

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20150623/25120d9c/attachment-0002.html>


More information about the discuss mailing list