diff options
| author | Dr. David Alan Gilbert | 2018-04-16 19:09:30 +0200 |
|---|---|---|
| committer | Juan Quintela | 2018-06-04 05:46:15 +0200 |
| commit | 0f073f44df109ea0910d67caede70dec95956ff6 (patch) | |
| tree | 6f519df95f4f8f982fb81def32752746948fb8e2 /include | |
| parent | migration: discard non-migratable RAMBlocks (diff) | |
| download | qemu-0f073f44df109ea0910d67caede70dec95956ff6.tar.gz qemu-0f073f44df109ea0910d67caede70dec95956ff6.tar.xz qemu-0f073f44df109ea0910d67caede70dec95956ff6.zip | |
migration: Don't activate block devices if using -S
Activating the block devices causes the locks to be taken on
the backing file. If we're running with -S and the destination libvirt
hasn't started the destination with 'cont', it's expecting the locks are
still untaken.
Don't activate the block devices if we're not going to autostart the VM;
'cont' already will do that anyway. This change is tied to the new
migration capability 'late-block-activate' that defaults to off, keeping
the old behaviour by default.
bz: https://bugzilla.redhat.com/show_bug.cgi?id=1560854
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions