| commit | 0746a92612276aee69e66dfe6782b0f882d221d5 | |
| author | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Wed, 28 Mar 2018 17:02:07 +0000 (28 18:02 +0100) | ||
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Thu, 29 Mar 2018 13:53:16 +0000 (29 14:53 +0100) | ||
| tree | 6f6dbaf375f303d0bf337dcc0c519006d41e1bf5 | treesnapshot (tar.gz zip) |
| parent | fc6008f37a6f5779fc8c723823861c43a0abfb44 | commitdiff |
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>
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>
| migration/migration.c | diffblobblamehistory |