[ovs-discuss] error: "could not open network device dpdk0 (Address family not supported by protocol)"

Ranjith Kumar D Ranjith.Kumar at radisys.com
Thu Sep 14 13:28:49 UTC 2017


Hello All,

I have installed OVS 2.4.0 in a Virtual machine with DPDK 2.0,  I am getting below error when I add DPDK port in OVS bridge.

error: "could not open network device dpdk0 (Address family not supported by protocol)"

d68d0789-5e61-47d4-ad2d-838c183b0e41
    Bridge pdn-br
        Port "dpdk0"
            Interface "dpdk0"
                type: dpdk
                error: "could not open network device dpdk0 (Address family not supported by protocol)"
        Port pdn-br
            Interface pdn-br
                type: internal

DPDK NIC status:

ubuntu at mysite-vpgwu-slice1-25:~/dpdk-2.0.0/tools$ ./dpdk_nic_bind.py --s

Network devices using DPDK-compatible driver
============================================
0000:00:03.0 'Virtio network device' drv=igb_uio unused=

Network devices using kernel driver
===================================
0000:00:04.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
0000:00:05.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
0000:00:06.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
0000:00:07.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio

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

Huge Page:( cat /proc/meminfo)

HugePages_Total:       1
HugePages_Free:        1
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB
DirectMap4k:       51068 kB
DirectMap2M:     3094528 kB
DirectMap1G:     7340032 kB


The below are steps which I followed to configure OVS


1.     config_file="/etc/depmod.d/openvswitch.conf"

2.     for module in datapath/linux/*.ko; do   modname="$(basename ${module})";   echo "override ${modname%.ko} * extra" >> "$config_file";   echo "override ${modname%.ko} * weak-updates" >> "$config_file";   done

3.     depmod -a

4.     /sbin/modprobe openvswitch

5.     /sbin/lsmod

6.     mkdir -p /usr/local/etc/openvswitch

7.     ovsdb-tool create /usr/local/etc/openvswitch/conf.db vswitchd/vswitch.ovsschema

8.     ovsdb-server --remote=punix:/usr/local/var/run/openvswitch/db.sock                  --remote=db:Open_vSwitch,Open_vSwitch,manager_options                  --private-key=db:Open_vSwitch,SSL,private_key                  --certificate=db:Open_vSwitch,SSL,certificate                  --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert                  --pidfile -detach

9.     ovs-vsctl --no-wait init

10.  ovs-vswitchd --pidfile -detach

11.  ovs-vsctl add-br pdn-br

12.  ovs-vsctl set bridge pdn-br datapath_type=netdev

13.  ovs-vsctl add-port pdn-br dpdk0 -- set Interface dpdk0 type=dpdk

The VM had hang when I follow below steps instead of above step 10


1.     export DB_SOCK=/usr/local/var/run/openvswitch/db.sock

2.     ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile -detach


Output VM hang console:

root at mysite-vpgwu-slice1-25:/home/ubuntu# ovs-vswitchd --dpdk -c 0x1 -n 4 -- unix:$DB_SOCK --pidfile -detach

2017-09-14T21:32:31Z|00001|dpdk|INFO|No -vhost_sock_dir provided - defaulting to /usr/local/var/run/openvswitch

EAL: Detected lcore 0 as core 0 on socket 0

EAL: Detected lcore 1 as core 0 on socket 0

EAL: Detected lcore 2 as core 0 on socket 0

EAL: Detected lcore 3 as core 0 on socket 0

EAL: Support maximum 128 logical core(s) by configuration.

EAL: Detected 4 lcore(s)

EAL: VFIO modules not all loaded, skip VFIO support...

EAL: Setting up memory...

debug2: channel 0: window 999344 sent adjust 49232

EAL: Ask a virtual area of 0x40000000 bytes

EAL: Virtual area found at 0x7f6700000000 (size = 0x40000000)

EAL: Requesting 1 pages of size 1024MB from socket 0

EAL: TSC frequency is ~1795841 KHz

EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !

EAL: Master lcore 0 is ready (tid=75c8db40;cpuset=[0])

PMD: ENICPMD trace: rte_enic_pmd_init

EAL: PCI device 0000:00:03.0 on NUMA socket -1

EAL:   probe driver: 1af4:1000 rte_virtio_pmd

EAL: PCI device 0000:00:04.0 on NUMA socket -1

EAL:   probe driver: 1af4:1000 rte_virtio_pmd

EAL: PCI device 0000:00:05.0 on NUMA socket -1

EAL:   probe driver: 1af4:1000 rte_virtio_pmd

EAL: PCI device 0000:00:06.0 on NUMA socket -1

EAL:   probe driver: 1af4:1000 rte_virtio_pmd

EAL: PCI device 0000:00:07.0 on NUMA socket -1

EAL:   probe driver: 1af4:1000 rte_virtio_pmd



Any input ?



Regards,

Ranjith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20170914/4afddb51/attachment-0001.html>


More information about the discuss mailing list