© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
Hi Torel,
as I said above the message is pretty generic - it would be the same for a whole category of migration issues [0]. Since you seem to be able to reproduce, and do so rather quickly the next steps would be:
- for migrations you always want to trace both sides as the root cause could be on source or target
- you'd want to get detailed logs of libvirt [1]
- you'd want to get logs of qemu (let libvirt add -D to a file) [2][3]
- guests are rather isolated by apparmor, you might need to allow it to write to that file [4]
Last but not least since you are on a pretty old libvirt (4.0 was bionic which is great but also 5 years old) you should try the very same activity with at least 22.04 Jammy and 23.04 Lunar. Chances are you have hit a fixed issue, if that is the case bisecting to what fixed it can be faster than reading massive logfiles over and over.
And since chances are quite low that you actually hit the very same issue as the initial reporter here I think filing with all that info as a new libvirt+qemu bug would be more appropriate.
[0]: https:/
[1]: https:/
[2]: https:/
[3]: https:/
[4]: ApparmorIsolation in https:/