RFC v1: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00912.html RFC v2: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00915.html
Branch: https://github.com/XanClic/qemu.git migration-bitmap-mapping-v1 Branch: https://git.xanclic.moe/XanClic/qemu.git migration-bitmap-mapping-v1 Hi, This new migration parameter allows mapping block node names and bitmap names to aliases for the purpose of block dirty bitmap migration. This way, management tools can use different node names on the source and destination and pass the mapping of how bitmaps are to be transferred to qemu (on the source, the destination, or even both with arbitrary aliases in the migration stream). v1 (as opposed to the RFC): - Added an iotest - Allow mapping of not only node names, but also of bitmap names to aliases - Make this a migration parameter instead of adding a whole new QMP command - Added patch 1 for good measure Max Reitz (4): migration: Prevent memleak by ...params_test_apply migration: Add block-bitmap-mapping parameter iotests.py: Add wait_for_runstate() iotests: Test node/bitmap aliases during migration qapi/migration.json | 83 +++++- migration/migration.h | 3 + migration/block-dirty-bitmap.c | 372 +++++++++++++++++++++---- migration/migration.c | 33 ++- tests/qemu-iotests/300 | 487 +++++++++++++++++++++++++++++++++ tests/qemu-iotests/300.out | 5 + tests/qemu-iotests/group | 1 + tests/qemu-iotests/iotests.py | 4 + 8 files changed, 931 insertions(+), 57 deletions(-) create mode 100755 tests/qemu-iotests/300 create mode 100644 tests/qemu-iotests/300.out -- 2.26.2
