I have been able to create a smaller recreation environment for this.
1. Create a VM on shared storage solution. In my case NFS.
2. set start_libvirtd="yes" in /etc/default/libvirt-bin
3. systemctl restart libvirt-bin
4. virsh -c qemu+ssh://${FROM}/system migrate --live --p2p --tunnelled ${VM}
qemu+tcp://ubuntu@${TO}/system
5. Repeat until failure to migrate, then check /var/log/libvirt/qemu/<vm>.log
for error from above.
* Yes --live, --p2p, and --tunnelled are all required to reproduce
afaik.
Using this reproducer I was able to identify upstream commit 4eae2a6 as
the first good SHA where the migration starts working again.
Unfortunately this does not cherry-pick cleanly, and it appears that the
virtqueue management has changed significantly as well. I'm currently
trying to figure what other patches are needed to make the qemu
virtqueue stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647389
Title:
Regression: Live migrations can still crash after CVE-2016-5403 fix
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
