Public bug reported: *as a start same text as my reach for the involved project mailing lists*
I was trying to replicate a setup that I have working on physical devices (ixgbe) under kvm since there is a virtio pmd driver. TL;DR: - under KVM with virtio-pci (working on baremetal with ixgbe cards) - adding dpdk port to ovs fails with memzone <port0_tvq0> already exists and causes a segfault - I couldn't find a solution in similar mails that popped up here recently, any help or pointer appreciated. ## Details ## I thought I've read that others have it working I thought that would be a great way to gain more debug control of the environment, but something seems to be eluding me. There were quite some similar mails on the List recently, but none seemed to hit the same issue as I do. At least none of the tunings/workarounds seemed to apply to me. As versions I have Openvswitch 2.5, DPDK 2.2, Qemu 2.5, Kernel 4.4 - so a fairly recent software stack. The super-short repro summary is: 1. starting ovs-dpdk like ovs-vswitchd --dpdk -c 0x1 -n 4 --pci-blacklist 0000:00:03.0 -m 2048 -- unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor 2. add a bridge and a ovs dpdk port ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk The log of the initialization after #1 looks good to me - I can see two of my three virtio devices recognized and one blacklisted. Memory allocation looks good, ... I'll attach the log at the end of the mail ## ISSUE ## But when I add a port and refer to one of the dpdk ports it fails with the following: ovs-vsctl[14023]: ovs|00001|vsctl|INFO|Called as ovs-vsctl add-port ovsdpdkbr0 dpdk0 -- set Interface dpdk0 type=dpdk ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone <port0_tvq0> already exists ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone <port0_tvq0_hdrzone> already exists ovs-vswitchd[13903]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone <port0_rvq0> already exists kernel: show_signal_msg: 18 callbacks suppressed kernel: pmd12[14025]: segfault at 2 ip 00007f3eb205eab2 sp 00007f3e3dffa590 error 4 in libdpdk.so.0[7f3eb1fdf000+1e9000] ovs-vswitchd[13902]: ovs|00003|daemon_unix(monitor)|ERR|1 crashes: pid 13903 died, killed (Segmentation fault), core dumped, restarting systemd-udevd[14040]: Could not generate persistent MAC address for ovs-netdev: No such file or directory kernel: device ovs-netdev entered promiscuous mode ovs-vswitchd[14036]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone <RG_MP_ovs_mp_1500_0_262144> already exists ovs-vswitchd[14036]: RING: Cannot reserve memory kernel: device ovsdpdkbr0 entered promiscuous mode ovs-vswitchd[14036]: EAL: memzone_reserve_aligned_thread_unsafe(): memzone <RG_MP_ovs_mp_1500_0_262144> already exists ovs-vswitchd[14036]: RING: Cannot reserve memory ## Experiments (failed) ## I thought it could be related to all the multiqueue chances that recently going in. My usual setup has 4 vCPUs and 4 queues per virtio-net device. I tried them with only 1 of 4 queues, also with only 1 queue defined and only 1 CPU - but all fail the same way. I have testpmd and l2fwd on the same devices working, so I hope they are not totally set up badly. I also tried hilarious things like reassigning to uio_pci_generic before, but well its virtio_pmd eventually anyways - so it made no difference. >From how it appears I felt that it could be related to the old discussions around [1] http://dpdk.org/ml/archives/dev/2015-May/017589.html [2] http://openvswitch.org/pipermail/dev/2015-March/052344.html But they are (partially) applied upstream already and the issue doesn't 100% match the old discussions. ## Logs ## [3] log of openvswitch start (attached for more readability) This needs to be debugged and fixed or openvswitch-dpdk it will be unusable within virtio environments. Upstream discussion started: http://dpdk.org/ml/archives/dev/2016-March/036021.html http://openvswitch.org/pipermail/discuss/2016-March/020488.html ** Affects: dpdk (Ubuntu) Importance: Critical Assignee: ChristianEhrhardt (paelzer) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559912 Title: Openvswitch 2.5 + dpdk 2.2 totally failing for virtio PMD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1559912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
