Chris, You're right, I executed:
ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 ...Within the KVM Guest and guess what? That is precisely what is crashing OVS+DPDK at the host! I removed IXIA out from the equation, not sending traffic now, all stopped. * Steps to reproduce (I'll update the original post soon) 1- Within the KVM Guest (original post reference, steps 7, 8 and 9): systemctl disable dpdk systemctl disable openvswitch-switch reboot ethtool -L ens5 combined 4 ethtool -L ens6 combined 4 ovs-vsctl add-br ovsbr -- set bridge ovsbr datapath_type=netdev ovs-vsctl add-port ovsbr dpdk0 -- set Interface dpdk0 type=dpdk ovs-vsctl add-port ovsbr dpdk1 -- set Interface dpdk1 type=dpdk So far, so good (slow but, not crashing)... ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4 BOOM! Now it crashes! Screenshot: http://i.imgur.com/2qREFET.png Easier to reproduce, no need for traffic (IXIA, for example). Cheers! Thiago ** Summary changed: - OVS+DPDK crashes at the host, right after starting another OVS+DPDK inside of a KVM Guest, easier to reproduce if multi-queue is enabled. + OVS+DPDK segfault at the host, after running "ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4" within a KVM Guest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577088 Title: OVS+DPDK segfault at the host, after running "ovs-vsctl set Open_vSwitch . other_config:n-dpdk-rxqs=4" within a KVM Guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1577088/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
