DescriptionTimothy Redaelli
2022-04-21 12:24:37 UTC
+++ This bug was initially created as a clone of Bug #2059758 +++
+++ This bug was initially created as a clone of Bug #2048601 +++
+++ This bug was initially created as a clone of Bug #2040292 +++
Description of problem:
The OSP deployment involves creation of 64 VFs on 4 CX4 ports (256 VFs), spread across 2 NUMA. A dpdk bond is created between VF0 of port 0 (NUMA0) and VF0 of port 3 (NUMA1). The port creation fails with below error.
Bridge br-link0
fail_mode: standalone
datapath_type: netdev
Port dpdkbond0
Interface dpdk1
type: dpdk
options: {dpdk-devargs="0000:d8:00.2", n_rxq="1"}
error: "Error attaching device '0000:d8:00.2' to DPDK"
Interface dpdk0
type: dpdk
options: {dpdk-devargs="0000:12:00.2", n_rxq="1"}
Port br-link0
Interface br-link0
type: internal
ovs_version: "2.13.4"
How reproducible:
As a quick reproducer with limited VFs, we could build Openvswitch with CONFIG_RTE_MAX_ETHPORTS set to 32 and create a user bridge with dpdk bonds involving a VF with higher order PCI address.
Actual results:
Port creation fails
Expected results:
Port creation shall be successful.
SOS reports are attached in the case.
PS: The port creations were successful when the customer went ahead with 32 VFs per port.