Hi Ian,
Thanks a lot for your patch. I applied your modifications and ran again the
setup described in the original post. While the CRC-related error message
has disappeared, openvswitch still crashes (with no gdb running!):
# tail ovs-vswitchd.log
2018-03-07T14:58:53.311Z|00215|dpdk|INFO|EAL:
Hi Ricardo,
Apologies for the delay. Unfortunately with the OVS 2.9 release I haven’t had
much time to look at this further.
At the very least I think work needs to be done for dpdk.c and netdev-dpdk.c to
enable configuration of VFs specifically (to account for the HW_CRC and VSI
queue
Hi Ricardo,
That’s for reporting the issue and providing the steps to reproduce.
I was able to reproduce this with an i40e VF using igb_uio.
In short it seems there is no support currently for ixgbe and i40e VF devices
in OVS with DPDK.
There are 2 issues at play here. First is the
Here are the steps to reproduce the issue:
1. Create one Virtual Function (VF) on a physical interface that supports
SR-IOV (in my case it's an Intel i350 interface):
$ echo 1 > /sys/class/net/eth10/device/sriov_numvfs
2. Lookup its PCI address, for example with dpdk-devbind.py:
$
Hi,
I was going through the openvswitch+dpdk tutorial and wanted to add a
virtual function (VF) to a bridge as a dpdk interface.
I can bind the VF to the vfio-pci driver successfully with dpdk-devbind.py,
but as soon as I add the interface to an ovs bridge (in netdev mode),
openvswitch goes in
