Bug 1394901 - Couldn't boot a VM - OVS2.5 + DPDK and VXLAN as tenant network type
Summary: Couldn't boot a VM - OVS2.5 + DPDK and VXLAN as tenant network type
Keywords:
Status: CLOSED DUPLICATE of bug 1295374
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch-dpdk
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Aaron Conole
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 16:41 UTC by Eyal Dannon
Modified: 2016-12-04 11:12 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-04 11:12:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Openvswitch's configuration (4.10 KB, text/plain)
2016-11-23 14:06 UTC, Eyal Dannon
no flags Details

Description Eyal Dannon 2016-11-14 16:41:20 UTC
Description of problem:

Part of OSPd10 OVS + DPDK verification I've tried to boot a VM with tenant network type - VXLAN.
The VM enters to ERROR state.
The main issue is [dpdk, dpdkr, dpdkvhostuser] are missing

# ovs-vsctl get Open_vSwitch . iface_types
[geneve, gre, internal, ipsec_gre, lisp, patch, stt, system, tap, vxlan]

[root@compute-0 ~]# ovs-vsctl show
5195c1b9-0793-48d2-ae2e-31a3f0a701e7
    Manager "ptcp:6640:127.0.0.1"
    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-link0"
            Interface "int-br-link0"
                type: patch
                options: {peer="phy-br-link0"}
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
    Bridge "br-link0"
        Controller "tcp:127.0.0.1:6633"
        fail_mode: secure
        Port "phy-br-link0"
            Interface "phy-br-link0"
                type: patch
                options: {peer="int-br-link0"}
        Port "dpdk0"
            Interface "dpdk0"
                type: dpdk
        Port "br-link0"
            Interface "br-link0"
                type: internal
    Bridge br-tun
        Controller "tcp:127.0.0.1:6633"
        fail_mode: secure
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "vxlan-0a0a8e6e"
            Interface "vxlan-0a0a8e6e"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.10.142.108", out_key=flow, remote_ip="10.10.142.110"}
    Bridge br-isolated
        Port "vlan542"
            tag: 542
            Interface "vlan542"
                type: internal
        Port br-isolated
            Interface br-isolated
                type: internal
        Port "vlan541"
            tag: 541
            Interface "vlan541"
                type: internal
        Port "ens2f0"
            Interface "ens2f0"
    Bridge br-ex
        Controller "tcp:127.0.0.1:6633"
        fail_mode: secure
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port br-ex
            Interface br-ex
                type: internal
    ovs_version: "2.5.0"


Version-Release number of selected component (if applicable):

OVS 
Name        : openvswitch
Arch        : x86_64
Version     : 2.5.0
Release     : 14.git20160727.el7fdp
Size        : 16 M
Repo        : installed
From repo   : rhos-10.0-rhel-7-fast-datapath

DPDK
Name        : dpdk
Arch        : x86_64
Version     : 2.2.0
Release     : 3.el7
Size        : 2.7 M
Repo        : installed
From repo   : rhos-10.0-rhel-7-extras-signed


How reproducible:
Always

Steps to Reproduce:
1.Setup environment with OVS, DPDK and VXLAN as tenant network type
2.Boot a VM

Actual results:
VM enters to ERROR state

Expected results:
VM Active and Running

Additional info:
2016-11-14T15:05:14.791Z|00219|netdev|WARN|could not create netdev dpdk0 of unknown type dpdk
2016-11-14T15:05:14.791Z|00220|bridge|WARN|could not open network device dpdk0 (Address family not supported by protocol)
2016-11-14T15:08:04.978Z|00221|rconn|INFO|br-link0<->tcp:127.0.0.1:6633: connection closed by peer
2016-11-14T15:08:04.979Z|00222|rconn|INFO|br-tun<->tcp:127.0.0.1:6633: connection closed by peer
2016-11-14T15:08:04.979Z|00223|rconn|INFO|br-ex<->tcp:127.0.0.1:6633: connection closed by peer
2016-11-14T15:08:04.979Z|00224|rconn|INFO|br-int<->tcp:127.0.0.1:6633: connection closed by peer
2016-11-14T15:08:05.355Z|00001|ofproto_dpif_xlate(handler388)|WARN|bridge br-isolated: received packet on unknown port 1
2016-11-14T15:08:05.383Z|00001|ofproto_dpif_upcall(handler404)|INFO|received packet on unassociated datapath port 2
2016-11-14T15:08:05.388Z|00001|ofproto_dpif_upcall(handler403)|INFO|received packet on unassociated datapath port 2
2016-11-14T15:08:05.478Z|00002|daemon_unix(monitor)|INFO|pid 1183 died, exit status 0, exiting

Comment 1 Aaron Conole 2016-11-14 18:26:35 UTC
You will need to add dpdk initialization to your /etc/sysconfig/openvswitch file (something like DPDK_OPTIONS="--dpdk -c 0x1 --") and restart the openvswitch service to enable these ports.

Please retry with the above config.

Comment 2 Eyal Dannon 2016-11-15 06:44:06 UTC
I've tried with those 3 DPDK_OPTIONS
DPDK_OPTIONS = "-l 2 -n 4 --socket-mem 1024 -w 0000:05:00.1"
DPDK_OPTIONS="--dpdk -c 0x2 -- "
DPDK_OPTIONS="--dpdk -c 0x2 -- --socket-mem 1024 -w 0000:05:00.1"

Having the same error.

Comment 5 Aaron Conole 2016-11-23 13:56:12 UTC
try:

DPDK_OPTIONS="--dpdk -l 2 -n 4 --socket-mem 1024 -w 0000:05:00.1 --"

If that doesn't work, may I have a look at the system in question?

Comment 6 Eyal Dannon 2016-11-23 14:06:50 UTC
Created attachment 1223247 [details]
Openvswitch's configuration

Now, I'm able to boot an instance but the tunneling doesn't work.

Comment 7 Terry Wilson 2016-11-30 21:48:17 UTC
br-link0 shouldn't be patched to br-int (bridge_mappings shouldn't contain bridges with dpdk ports for vxlan to work)

Comment 8 Eyal Dannon 2016-12-04 11:12:31 UTC
I'm closing this bug as duplication of Bug No.1295374

*** This bug has been marked as a duplicate of bug 1295374 ***


Note You need to log in before you can comment on or make changes to this bug.