Re: [libvirt PATCH 14/80] qemu: Keep migration job active after failed post-copy

2022-05-13 Thread Jiri Denemark
On Wed, May 11, 2022 at 14:35:22 +0200, Peter Krempa wrote: > On Tue, May 10, 2022 at 17:20:35 +0200, Jiri Denemark wrote: > > When post-copy migration fails, we can't just abort the migration and > > resume the domain on the source host as it is already running on the > > destination host and no

Re: [libvirt PATCH 14/80] qemu: Keep migration job active after failed post-copy

2022-05-11 Thread Peter Krempa
On Tue, May 10, 2022 at 17:20:35 +0200, Jiri Denemark wrote: > When post-copy migration fails, we can't just abort the migration and > resume the domain on the source host as it is already running on the > destination host and no host has a complete state of the domain memory. > Instead of the

[libvirt PATCH 14/80] qemu: Keep migration job active after failed post-copy

2022-05-10 Thread Jiri Denemark
When post-copy migration fails, we can't just abort the migration and resume the domain on the source host as it is already running on the destination host and no host has a complete state of the domain memory. Instead of the current approach of just marking the domain on both ends as