From: Nikita Lapshin <nikita.lapshin@openvz.org>
We want to implement exteranl bg-snapshot tool for saving RAM. For this it
is important to be able manage migration stream because tool has no idea
about non-RAM part and how to parse it.
This paramter provides gurantee about migration content. Now there are 4
parts of migration stream which can be specified: "ram", "block",
"dirty-bitmaps", "vmstate". "vmstate" can be any section which handler has
vmdesc. "block" and "dirty-bitmpas" impleneted just like existing
capabilities.
This way of specifying can be extended on future parts of migration.
Nikita Lapshin (8):
migration: Implemented new parameter stream_content
migration: should_skip() implemented
migration: Add vmstate part of migration stream
migration: Add dirty-bitmaps part of migration stream
migration: Add block part of migration stream
migration: Add RAM part of migration stream
migration: analyze-migration script changed
migration: Test for RAM and vmstate parts
migration/migration.c | 76 ++++++++++++++-
migration/migration.h | 3 +
migration/ram.c | 6 ++
migration/savevm.c | 69 ++++++++-----
qapi/migration.json | 21 +++-
scripts/analyze-migration.py | 19 ++--
.../tests/migrate-ram-stream-content-test | 96 +++++++++++++++++++
.../tests/migrate-ram-stream-content-test.out | 5 +
8 files changed, 256 insertions(+), 39 deletions(-)
create mode 100755 tests/qemu-iotests/tests/migrate-ram-stream-content-test
create mode 100644 tests/qemu-iotests/tests/migrate-ram-stream-content-test.out
--
2.31.1