ovs-dpdk is not working with mlx (current OFED + new)

Bug #1964241 reported by Steven Webster
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Triaged
Low
Unassigned

Bug Description

Brief Description:

It appears that ovs-dpdk using Mellanox (CX-4/5) data interfaces is not currently working with StarlingX:

[sysadmin@compute-0 ~(keystone_admin)]$ system host-if-list compute-0
------------------------------------{}------{}+{}------{}{}------{}{}--{}{}-----------{}{}-----------{}{}----------------{}+{}-------------------------

uuid name class type vlan ports uses i/f used by i/f attributes
                                                            id
------------------------------------{}------{}+{}------{}{}------{}{}--{}{}-----------{}{}-----------{}{}----------------{}+{}-------------------------

35c98815-a6a2-4077-b43f-72013606b7e3 mgmt0 platform vlan 150 [] [u'pxeboot0'] [] MTU=1500
3e1e2f77-1f2f-4f71-ac4e-26f7466f3bf9 data0 data ethernet None [u'ens785f1'] [] [] MTU=9216,accelerated=True
5398871c-97da-4807-90cd-2ef613a36ea0 pxeboot0 platform ethernet None [u'ens785f0'] [] [u'mgmt0', MTU=9216
                                                                                              u'cluster0']

aa44b4ae-6b02-4af4-86f2-4e326adcb185 cluster0 platform vlan 151 [] [u'pxeboot0'] [] MTU=1500
------------------------------------{}------{}+{}------{}{}------{}{}--{}{}-----------{}{}-----------{}{}----------------{}+{}-------------------------

#Lock

system host-lock compute-0

Assign host-labels to enable the vswitch to start
system host-label-assign compute-0 openstack-control-plane=enabled

system host-label-assign compute-0 openstack-compute-node=enabled

 system host-label-assign compute-0 openvswitch=enabled

Set system vswitch type, 1G hugepages and at least one dedicated cpu on each socket dedicated to vswitch
 system modify --vswitch_type ovs-dpdk

system host-memory-modify compute-0 -f vswitch 0 -1G 2

system host-memory-modify compute-0 -f vswitch 1 -1G 2

 system host-cpu-modify -f vswitch -p0 1 compute-0

 system host-cpu-modify -f vswitch -p1 1 compute-0

#Unlock

system host-unlock compute-0

Run command "sudo ovs-vsctl show" in compute-0 after it is online.

compute-0:~$ sudo ovs-vsctl show
Password:
9b3183fa-1956-4b91-b108-acf7b557ec1f
    Bridge "br-phy0"
        Port "br-phy0"
            Interface "br-phy0"
                type: internal
        Port "eth0"
            Interface "eth0"
                type: dpdk
                options: {dpdk-devargs="0000:05:00.1", n_rxq="2"}
                error: "Error attaching device '0000:05:00.1' to DPDK"
        Port "lldp466a1880-9c"
            Interface "lldp466a1880-9c"
                type: internal
    ovs_version: "2.11.0"

The current MLX driver has been tested, as well as the new OFED version: https://review.opendev.org/c/starlingx/kernel/+/831461

Revision history for this message
Ghada Khalil (gkhalil) wrote :

screening: low priority; issue has been there for a while. No complaints from users which means nobody is likely using this config.

Changed in starlingx:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.