Re: [Xen-devel] Re: pv_ops dom0 USB fixed

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Fri, 2008-12-12 at 09:12 +0000, Andrew Lyon wrote:
> (XEN) Xen-e820 RAM map:
> (XEN)  0000000000000000 - 000000000009ec00 (usable)
> (XEN)  00000000000f0000 - 0000000000100000 (reserved)
> (XEN)  0000000000100000 - 00000000cfdff800 (usable)
> (XEN)  00000000cfdff800 - 00000000cfe53c00 (ACPI NVS)
> (XEN)  00000000cfe53c00 - 00000000cfe55c00 (ACPI data)
> (XEN)  00000000cfe55c00 - 00000000d0000000 (reserved)
> (XEN)  00000000e0000000 - 00000000f0000000 (reserved)
> (XEN)  00000000fec00000 - 00000000fed00400 (reserved)
> (XEN)  00000000fed20000 - 00000000feda0000 (reserved)
> (XEN)  00000000fee00000 - 00000000fef00000 (reserved)
> (XEN)  00000000ffb00000 - 0000000100000000 (reserved)
> (XEN)  0000000100000000 - 0000000128000000 (usable)
> BIOS-provided physical RAM map:
>  Xen: 0000000000000000 - 00000000000a0000 (usable)
>  Xen: 00000000000a0000 - 0000000000100000 (reserved)
>  Xen: 0000000000100000 - 000000000087d000 (usable)
>  Xen: 000000000087d000 - 0000000000fd1000 (reserved)
>  Xen: 0000000000fd1000 - 00000000ea567000 (usable)

It's only peripherally related (and a bit of a stab in the dark) but
since you have plenty of host RAM your pseudo-physical addresses overlap
with the ACPI tables and such so it would be worth trying out the patch
I just pushed to reserve these. Although I saw actual warnings and you
don't seem to it's possible there are other failures due to the
conflicts. Alternatively you could try limiting the domain 0 memory,
e.g. with dom0_mem=3G on the Xen command line.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel