mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 02:01:24 +01:00
Juergen Gross
76a68b9020
Today the memory size of dom0 can be specified only in terms of bytes (either an absolute value or "host-mem - value"). When dom0 shouldn't be auto-ballooned this requires nearly always a manual adaption of the Xen boot parameters to reflect the actual host memory size. Add more possibilities to specify memory sizes. Today we have: dom0_mem= List of ( min:<size> | max:<size> | <size> ) with <size> being a positive or negative size value (e.g. 1G). Modify that to: dom0_mem= List of ( min:<sz> | max:<sz> | <sz> ) <sz>: <size> | [<size>+]<frac>% <frac>: integer value < 100 With the following semantics: <frac>% specifies a fraction of host memory size in percent. <sz> is a percentage of host memory plus an offset. So <sz> being 1G+25% on a 256G host would result in 65G. Signed-off-by: Juergen Gross <jgross@suse.com> Reviewed-by: Jan Beulich <jbeulich@suse.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.