migration: support migration with image files
Status from this message: Applied.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | migrate: add migration blockersmigration.c migration.h | +33 | 1 reply | |
| 2/5 | ivshmem: use migration blockers to prevent live migration in peer mode (v2)hw/ qerror.c qerror.h +2 more | +628 | 2 replies | |
| 3/5 | block: allow migration to work with image files (v3)block.c block.h block_int.h +1 more | +28 | 0 replies | |
| 4/5 | qcow2: implement bdrv_invalidate_cache (v2)block/ block/ | +36 | 0 replies | |
| 5/5 | qed: add migration blocker (v2)block/ block/ qemu-tool.c +2 more | +28 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Qemu-devel] [PATCH 0/5] migration: support migration with image files
This series allows live migration to work with image formats. This series has two parts. The first part adds a new error infrastructure to migration which allows for different subsystems (other than qdev) to block migration when specific features are in use.
The second part adds block interfaces to flush metadata with image formats.
The migration error infrastructure is a no brainer for 1.0. It significantly improves the user experience and prevents a user from doing things that will cause a VM to crash during migration.
I'm less comfortable with the block interface for flushing metadata for 1.0. The code is completely isolated to the image formats and live migration. It should have no impact on normal use of an image format or live migration with raw images. That makes the risk for this very, very low.
Moreover, I'm sympathetic to the argument that this is a required feature for a 1.0 release. Image formats are a fairly normal way to use QEMU and not supporting live migration in this scenario means that live migration won't work for a large portion of QEMU's users.