Re: [Xen-devel] [PATCH v10 14/15] docs: libxc migration stream specification

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Tue, 2015-05-05 at 14:04 +0100, Andrew Cooper wrote:
> On 05/05/15 14:03, Ian Campbell wrote:
> > On Thu, 2015-04-23 at 12:48 +0100, Andrew Cooper wrote:
> >> From: David Vrabel <david.vrabel@xxxxxxxxxx>
> >>
> >> Add the specification for a new migration stream format.  The document
> >> includes all the details but to summarize:
> >>
> >> The existing (legacy) format is dependant on the word size of the
> >> toolstack.  This prevents domains from migrating from hosts running
> >> 32-bit toolstacks to hosts running 64-bit toolstacks (and vice-versa).
> >>
> >> The legacy format lacks any version information making it difficult to
> >> extend in compatible way.
> >>
> >> The new format has a header (the image header) with version information,
> >> a domain header with basic information of the domain and a stream of
> >> records for the image data.
> >>
> >> The format will be used for future domain types (such as on ARM).
> >>
> >> The specification is pandoc format (an extended markdown format) and the
> >> documentation build system is extended to support pandoc format documents.
> >>
> >> Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx>
> >> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> > Without reading:
> >
> > Acked-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
> >
> > With two minor comments:
> >
> >> diff --git a/docs/specs/libxc-migration-stream.pandoc 
> >> b/docs/specs/libxc-migration-stream.pandoc
> >> new file mode 100644
> >> index 0000000..455d1ce
> >> --- /dev/null
> >> +++ b/docs/specs/libxc-migration-stream.pandoc
> >> @@ -0,0 +1,672 @@
> >> +% LibXenCtrl Domain Image Format
> >> +% David Vrabel <<david.vrabel@xxxxxxxxxx>>
> >> +  Andrew Cooper <<andrew.cooper3@xxxxxxxxxx>>
> >> +% Draft G
> > No longer a draft? Perhaps s/Draft/Version/?
> 
> Strictly speaking it is still a draft until migration v2 becomes enabled
> by default.  This is one of the areas I was going to cover with my
> post-libxl cleanup patches.

Good point & sounds good, thanks.

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel