docs/migration Specify migration v3 and STATIC_DATA_END
authorAndrew Cooper <andrew.cooper3@citrix.com>
Thu, 5 Dec 2019 15:57:13 +0000 (15:57 +0000)
committerAndrew Cooper <andrew.cooper3@citrix.com>
Fri, 29 May 2020 16:33:03 +0000 (17:33 +0100)
commit6f71b5b150615ad97405605596af658697b05a00
tree70d41937f1a0674a941acb41740c541ce84212d9
parent7bac300b42a407cb9f4c07431997267c5264cbc1
docs/migration Specify migration v3 and STATIC_DATA_END

Migration data can be split into two parts - that which is invariant of
guest execution, and that which is not.  Separate these two with the
STATIC_DATA_END record.

The short term, we want to move the x86 CPU Policy data into the stream.
In the longer term, we want to provisionally send the static data only
to the destination as a more robust compatibility check.  In both cases,
we will want a callback into the higher level toolstack.

Mandate the presence of the STATIC_DATA_END record, and declare this v3,
along with instructions for how to compatibly interpret a v2 stream.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
docs/specs/libxc-migration-stream.pandoc
tools/libxc/xc_sr_common.c
tools/libxc/xc_sr_stream_format.h
tools/python/xen/migration/libxc.py