mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
Ian Jackson
bc1bd8ebc3
Right now, this is broken because libxl__build_device_model_args_new is used also for the qemu run for pv guests for qdisk devices, pvfb, etc. We can either make this option properly HVM-specific, or make it generic. In principle it is a reasonable request, to make the PV qemu deprivileged (even though it is not likely to be implemented any time soon). So make this option generic. We retain the name "device model" even though it is arguably inaccurate, because the xl docs already say, for example For a PV guest a device-model is sometimes used to provide backends for certain PV devices The documentation patch here is pure code motion. For ease of review we will fix up the docs, so the wording to be right for the new context, in the next patch. Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com> Reported-by: Roger Pau Monné <roger.pau@citrix.com> Acked-by: Wei Liu <wei.liu2@citrix.com> --- v2: Change xl too, to avoid breaking the build. Fix manpage pod syntax.
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.