Steps: Following steps of Description. We tested with Live migration with ovs+vhost-user+dpdk scenarios. Reproduced with openvswitch2.12-2.12.0-4.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-05T11:30:16.928011Z 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-05T11:30:17.779992Z 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-05T11:30:32.809076Z qemu-kvm: VQ 0 size 0x400 < last_avail_idx 0x5865 - used_idx 0x9274 2020-02-05T11:30:32.809109Z qemu-kvm: Failed to load virtio-net:virtio 2020-02-05T11:30:32.809127Z qemu-kvm: error while loading state for instance 0x0 of device '0000:00:06.0:00.0/virtio-net' 2020-02-05T11:30:32.811169Z qemu-kvm: load of migration failed: Operation not permitted Verified with openvswitch2.12-2.12.0-21.el7fdp.x86_64: # /bin/virsh migrate --verbose --persistent --live rhel7.8 qemu+ssh://10.73.72.196/system Migration: [100 %] Migration works very well. There is no any error. So this bug has been fixed very well. Move to 'VERIFIED'.
We also tested rhel8 version, this issue has been fixed well too. openvswitch2.12-2.12.0-21.el8fdp.x86_64 works well.
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:0745