Note: Given that this issue occurs in standalone dpdk it should likely be fixed in ovs-dpdk as well
I'm afraid I don't have an OVS setup to test on, do you happen to have one I can use?
Not really, I would just set up an OVS with two vhost interfaces, connect a qemu instance to each of them and perform the live migration while the guest is transmitting over the vhost interface. I can attach some scripts I used to reproduce a similar issue. Thanks!
Steps: Following steps of Description. We tested with Live migration with ovs+vhost-user+dpdk scenarios. Reproduced with openvswitch-2.9.0-124.el7fdp.x86_64. # /bin/virsh migrate --verbose --persistent --live rhel7.8 qemu+ssh://10.73.72.196/system Migration: [100 %]error: internal error: qemu unexpectedly closed the monitor: 2020-02-05T05:48:14.685282Z qemu-kvm: -chardev socket,id=charnet1,path=/tmp/vhostuser0.sock,server: info: QEMU waiting for connection on: disconnected:unix:/tmp/vhostuser0.sock,server 2020-02-05T05:48:15.121134Z qemu-kvm: -chardev socket,id=charnet2,path=/tmp/vhostuser1.sock,server: info: QEMU waiting for connection on: disconnected:unix:/tmp/vhostuser1.sock,server 2020-02-05T05:48:30.260841Z qemu-kvm: VQ 0 size 0x400 < last_avail_idx 0x38ad - used_idx 0x4cb6 2020-02-05T05:48:30.261044Z qemu-kvm: Failed to load virtio-net:virtio 2020-02-05T05:48:30.261061Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:06.0:00.0/virtio-net' 2020-02-05T05:48:30.263631Z qemu-kvm: load of migration failed: Operation not permitted Verified with openvswitch-2.9.0-125.el7fdp.x86_64: # /bin/virsh migrate --verbose --persistent --live rhel7.8 qemu+ssh://10.73.72.196/system Migration: [100 %] So this bug has been fixed very well. Note: We hit other migration issue which below bug is tracking. Bug 1791267 - Guest vhost-user ports stop receiving MoonGen packets after migration
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0742
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days