mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
In order to support pvgrub (or other bootloader) from dom0 chainloading a pvgrub (or other) from within the domU filesystem we need a standard for where the stage 1 bootloader should look and what it should expect to find there. Add a document along those lines. This is currently x86-specific since it is expected that other new architecures (including ARM) will either not need to implement this due to the existence of more generic specifications for that arch (e.g. the ARM VM spec) or will update this document in due course. Signed-off-by: Ian Campbell <ijc@hellion.org.uk> Acked-by: Ian Jackson <Ian.Jackson@eu.citrix.com> Cc: Colin Watson <cjwatson@debian.org> Cc: 759018@bugs.debian.org
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.