| commit | 5aaac46793828d01c893b9d99d905c657f59541e | |
| author | Paolo Bonzini <pbonzini@redhat.com> | |
| Wed, 14 Nov 2018 09:48:00 +0000 (14 10:48 +0100) | ||
| committer | Paolo Bonzini <pbonzini@redhat.com> | |
| Tue, 27 Nov 2018 14:06:14 +0000 (27 15:06 +0100) | ||
| tree | 6cffbf47336ee06c5a92c247ee6a779e28120f92 | treesnapshot (tar.gz zip) |
| parent | 56333e69ee1855a8fa74b361742a0a79407846d2 | commitdiff |
migration: savevm: consult migration blockers
There is really no difference between live migration and savevm, except
that savevm does not require bdrv_invalidate_cache to be implemented
by all disks. However, it is unlikely that savevm is used with anything
except qcow2 disks, so the penalty is small and worth the improvement
in catching bad usage of savevm.
Only one place was taking care of savevm when adding a migration blocker,
and it can be removed.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
There is really no difference between live migration and savevm, except
that savevm does not require bdrv_invalidate_cache to be implemented
by all disks. However, it is unlikely that savevm is used with anything
except qcow2 disks, so the penalty is small and worth the improvement
in catching bad usage of savevm.
Only one place was taking care of savevm when adding a migration blocker,
and it can be removed.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
| migration/savevm.c | diffblobblamehistory | |
| target/i386/kvm.c | diffblobblamehistory |