Re: [ovs-discuss] segmentation fault when adding a VF in DPDK to a switch

2018-03-08 Thread Stokes, Ian
Hi Riccardo, So the issue you are seeing is not related to the VSI queue setup as previously mentioned. The issue you see is specific to the use of the i350 VF with OVS it seems. Specifically, OVS attempts to set the MTU of a given device (in this case the SRIOV VF from an i350 interface

Re: [ovs-discuss] segmentation fault when adding a VF in DPDK to a switch

2018-03-07 Thread Riccardo Ravaioli
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:

Re: [ovs-discuss] segmentation fault when adding a VF in DPDK to a switch

2018-02-01 Thread Stokes, Ian
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

Re: [ovs-discuss] segmentation fault when adding a VF in DPDK to a switch

2018-01-11 Thread Stokes, Ian
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

Re: [ovs-discuss] segmentation fault when adding a VF in DPDK to a switch

2018-01-11 Thread Riccardo Ravaioli
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: $