Comment 9 for bug 2015533

Now, I still haven't looked at the segfaults, but I initially
couldn't reproduce them with just the dpdk pkg version change.

(And they didn't always happen / correlate with the traffic
interruption, so it does seem to be another problem.)

So, "just" library version incompatibility/interface breakage
on different ends such as QEMU/OVS/DPDK/RTE doesn't seem to be
the issue (which is likely reassured as there are no related
bugs/fixes to the DPDK packages in Bionic for a long time now;
so it seems to be a corner case).

Thus it _might_ be some weird state left in the VMs virtio-net
driver, that eventually got to talk back to DPDK vhost ports,
and provided it wrong pointers... or some unexpected state
as part of restarts of different components.

This needs more assessment and information to determine next steps.

For starters, it'd be nice to know what's the kernel version
running in the VMs to check the virtio-net driver level and
features negotiated with the hypervisor's vhost side.

Marking dpdk as Incomplete.