* Marc-André Lureau (marcandre.lur...@redhat.com) wrote:
> Explain how to use analyze-migration.py, this may help.
>
> Signed-off-by: Marc-André Lureau <marcandre.lur...@redhat.com>
Queued
> ---
> docs/devel/migration.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/docs/devel/migration.rst b/docs/devel/migration.rst
> index e88918f7639..2eb08624fc3 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.0.rc2.42.g98cedd0233
>
>
--
Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
