diff options
| author | Peter Xu <peterx@redhat.com> | 2024-12-06 18:08:35 -0500 |
|---|---|---|
| committer | Fabiano Rosas <farosas@suse.de> | 2025-01-09 17:38:48 -0300 |
| commit | fca9aef1c8d8fc4482cc541638dbfac76dc125d6 (patch) | |
| tree | 11891ee2af9ee8b150bb0832bad9c2689cfd3530 /scripts/analyze-migration.py | |
| parent | e4e5e89bbd8e731e86735d9d25b7b5f49e8f08b6 (diff) | |
| download | focaccia-qemu-fca9aef1c8d8fc4482cc541638dbfac76dc125d6.tar.gz focaccia-qemu-fca9aef1c8d8fc4482cc541638dbfac76dc125d6.zip | |
migration/block: Make late-block-active the default
Migration capability 'late-block-active' controls when the block drives will be activated. If enabled, block drives will only be activated until VM starts, either src runstate was "live" (RUNNING, or SUSPENDED), or it'll be postponed until qmp_cont(). Let's do this unconditionally. There's no harm to delay activation of block drives. Meanwhile there's no ABI breakage if dest does it, because src QEMU has nothing to do with it, so it's no concern on ABI breakage. IIUC we could avoid introducing this cap when introducing it before, but now it's still not too late to just always do it. Cap now prone to removal, but it'll be for later patches. Signed-off-by: Peter Xu <peterx@redhat.com> Reviewed-by: Fabiano Rosas <farosas@suse.de> Message-Id: <20241206230838.1111496-4-peterx@redhat.com> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Diffstat (limited to 'scripts/analyze-migration.py')
0 files changed, 0 insertions, 0 deletions