Discussing with Thomas Monjalon revealed a set of post 2.2 patches. These will no more let you intialize DPDK while a kernel driver - like virtio-pci is still bound.
I already proved before on this bug that reinitializing it to virtio-pci will properly set it up and make it workable again. So I intend to backport and test those patches together with some more for the next upload. This might need some more Doc updates and also will get rid of users accidentially killing their connection by failing to blacklist their main virtio device Thanks to Thomas for identifying these. @Martin - until then the proper "workaround" is to reinitialize via e.g.: dpdk_nic_bind -b uio_pci_generic 0000:00:04.0 dpdk_nic_bind -b virtio-pci 0000:00:04.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570195 Title: Net tools cause kernel soft lockup after DPDK touched VirtIO-pci devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1570195/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
