Hi Björn, reverse migrations (2.11 -> 2.8) are discouraged and to my knowledge never really supported by anyone (neither Upstream nor Distributions). OTOH lets look at the case still, but a bit more info might be useful.
You should enable [1] libvirtd debugging for the daemons on both sides of the migration. Something like: log_outputs="1:file:/var/log/libvirt/libvirtd.log" in your conf and then restarting them. With that in place trigger a failing migration and attach the follwing files here: /var/log/libvirt/libvirtd.log (source) /var/log/libvirt/libvirtd.log (target) /var/log/libvirt/qemu/<guestname>.log (source) /var/log/libvirt/qemu/<guestname>.log (target) Also the output of the console that you issue your migration command might be useful, so please add that as well. Note: Unlikely for your case, but I've seen local-storage migrations failing due to it sometimes, so if you have enabled and enforced apparmor for libvirt/guests check dmesg for denies. [1]: https://libvirt.org/logging.html
