ovs-dpdk is not working with mlx (current OFED + new)
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
-------
35c98815-
3e1e2f77-
5398871c-
aa44b4ae-
-------
#Lock
system host-lock compute-0
Assign host-labels to enable the vswitch to start
system host-label-assign compute-0 openstack-
system host-label-assign compute-0 openstack-
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-
Bridge "br-phy0"
Port "br-phy0"
Port "eth0"
Port "lldp466a1880-9c"
ovs_version: "2.11.0"
The current MLX driver has been tested, as well as the new OFED version: https:/
screening: low priority; issue has been there for a while. No complaints from users which means nobody is likely using this config.