From: Marc-André Lureau <marcandre.lur...@redhat.com>
Explain how to use analyze-migration.py, this may help.
Signed-off-by: Marc-André Lureau <marcandre.lur...@redhat.com>
Message-Id: <20200330174852.456148-1-marcandre.lur...@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
---
docs/devel/migration.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst
index e88918f763..2eb08624fc 100644
--- a/docs/devel/migration.rst
+++ b/docs/devel/migration.rst
@@ -50,6 +50,26 @@ All these migration protocols use the same infrastructure to
save/restore state devices. This infrastructure is shared with the
savevm/loadvm functionality.
+Debugging
+=========
+
+The migration stream can be analyzed thanks to `scripts/analyze_migration.py`.
+
+Example usage:
+
+.. code-block:: shell
+
+ $ qemu-system-x86_64
+ (qemu) migrate "exec:cat > mig"
+ $ ./scripts/analyze_migration.py -f mig
+ {
+ "ram (3)": {
+ "section sizes": {
+ "pc.ram": "0x0000000008000000",
+ ...
+
+See also ``analyze_migration.py -h`` help for more options.
+
Common infrastructure
=====================
--
2.26.2
