Re: [Xen-devel] [Xen-users] xl info displays less ram than the total available

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 05.10.16 at 15:32, <blallo@xxxxxxxxxx> wrote:
> Here it comes xl dmesg with Xen booted with e820-verbose=true

I have to admit that the only way I can see

(XEN) Initial Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009ec00 (usable)
(XEN)  000000000009ec00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 0000000079cbe000 (usable)
(XEN)  0000000079cbe000 - 00000000bcd2f000 (reserved)
(XEN)  00000000bcd2f000 - 00000000bce7f000 (ACPI NVS)
(XEN)  00000000bce7f000 - 00000000bceff000 (ACPI data)
(XEN)  00000000bceff000 - 00000000bfa00000 (reserved)
(XEN)  00000000f8000000 - 00000000fc000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fed08000 - 00000000fed09000 (reserved)
(XEN)  00000000fed10000 - 00000000fed18000 (reserved)
(XEN)  00000000fed18000 - 00000000fed19000 (reserved)
(XEN)  00000000fed19000 - 00000000fed1a000 (reserved)
(XEN)  00000000fed1c000 - 00000000fed20000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffc00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 000000043e600000 (reserved)

having all those reserved regions above 2Gb is for the boot
loader to behave oddly. Since Linux and Xen use different paths
in the boot loader, one can't really draw conclusions from Linux
getting to see a better memory map.

Jan


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