diff options
author | Kevin Wolf <kwolf@redhat.com> | 2017-05-22 17:10:38 +0200 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2017-06-09 11:45:03 +0200 |
commit | f07fa4cbf0b16426dc5a03d4e13943143eaeb1ce (patch) | |
tree | 1e09dd4101e026bc550540e890dbb8b001029422 /disas/microblaze.c | |
parent | 93c26503e01808bfb8cea3c25eae5be63147380e (diff) |
migration: Inactivate images after .save_live_complete_precopy()
Block migration may still access the image during its
.save_live_complete_precopy() implementation, so we should only
inactivate the image afterwards.
Another reason for the change is that inactivating an image fails when
there is still a non-device BlockBackend using it, which includes the
BBs used by block migration. We want to give block migration a chance to
release the BBs before trying to inactivate the image (this will be done
in another patch).
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Jeff Cody <jcody@redhat.com>
Diffstat (limited to 'disas/microblaze.c')
0 files changed, 0 insertions, 0 deletions