qemu-e2k/migration
Dr. David Alan Gilbert 0746a92612 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.

bz: https://bugzilla.redhat.com/show_bug.cgi?id=1560854
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-Id: <20180328170207.49512-1-dgilbert@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
2018-03-29 14:53:16 +01:00
..
Makefile.objs
block-dirty-bitmap.c
block.c
block.h
channel.c
channel.h
colo-comm.c
colo-failover.c
colo.c
exec.c
exec.h
fd.c
fd.h
global_state.c
migration.c migration: Don't activate block devices if using -S 2018-03-29 14:53:16 +01:00
migration.h
page_cache.c
page_cache.h
postcopy-ram.c
postcopy-ram.h
qemu-file-channel.c
qemu-file-channel.h
qemu-file.c
qemu-file.h
qjson.c
qjson.h
ram.c
ram.h
rdma.c
rdma.h
savevm.c
savevm.h
socket.c
socket.h
tls.c
tls.h
trace-events
vmstate-types.c
vmstate.c
xbzrle.c
xbzrle.h