Hi Thiago, I have used multiqueue in the guest in the way: Host+OVS+DPDK | | multiqueue (4) | v Guest
Not sure if you use DPDK in the guest as well in your case. But the former worked well for me. But IIRC from mailing list discussions the DPDK vhost user still doesn't like if you change the number of queues too often. I could boot and got up to #cpus queues auto-enabled and that worked. A while ago I found that they at least fixed the issues I had with changing the queue number via ethtool then - but not sure if your case still triggers something in there. You might catch me out on IRC - but next week I'm on a business trip - we might sync on our setup and identify if there is something to "fix in your setup" or "to reproduce in mine". -- 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 interface dpdk0 options:n_rxq=2 " within a KVM Guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1577088/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
