mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
David Vrabel
edfb555d86
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@citrix.com> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> Acked-by: Ian Campbell <Ian.Campbell@citrix.com>
xen-bugtool =========== The xen-bugtool command line application will collate the Xen dmesg output, details of the hardware configuration of your machine, information about the build of Xen that you are using, plus, if you allow it, various logs. The information collated can either be posted to a Xen Bugzilla bug (this bug must already exist in the system, and you must be a registered user there), or it can be saved as a .tar.bz2 for sending or archiving. The collated logs may contain private information, and if you are at all worried about that, you should not use this tool, or you should explicitly exclude those logs from the archive. xen-bugtool is wholly interactive, so simply run it, and answer the questions.