| commit | fb14a42ade228e2d6123af56c0015262fd83250d | |
| author | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Mon, 7 Oct 2019 10:35:07 +0000 (7 11:35 +0100) | ||
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Fri, 11 Oct 2019 13:25:26 +0000 (11 14:25 +0100) | ||
| tree | e32bc79b7ae4b04b75388422d3b57a6cdb2facae | treesnapshot (tar.gz zip) |
| parent | 694ea274d9236cada361282960e3a0aba660dee5 | commitdiff |
migration: Don't try and recover return path in non-postcopy
In normal precopy we can't do reconnection recovery - but we also
don't need to, since you can just rerun migration.
At the moment if the 'return-path' capability is on, we use
the return path in precopy to give a positive 'OK' to the end
of migration; however if migration fails then we fall into
the postcopy recovery path and hang. This fixes it by only
running the return path in the postcopy case.
Reported-by: Greg Kurz <groug@kaod.org>
Tested-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
In normal precopy we can't do reconnection recovery - but we also
don't need to, since you can just rerun migration.
At the moment if the 'return-path' capability is on, we use
the return path in precopy to give a positive 'OK' to the end
of migration; however if migration fails then we fall into
the postcopy recovery path and hang. This fixes it by only
running the return path in the postcopy case.
Reported-by: Greg Kurz <groug@kaod.org>
Tested-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
| migration/migration.c | diffblobblamehistory |