WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: pv_ops dom0 USB fixed
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Fri, 12 Dec 2008 11:15:07 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Aviv Grafi <aviv@xxxxxxxxxxxx>
Delivery-date: Fri, 12 Dec 2008 03:15:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0812120112y13e74752kbd3d17d7daa98848@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <4940210C.1060401@xxxxxxxx> <1e16a9ed0812110850odff8f56h836b7187ad0c64b0@xxxxxxxxxxxxxx> <49415945.3030508@xxxxxxxx> <1e16a9ed0812111147h3416cbb5uc11a8b9f5f0d0e80@xxxxxxxxxxxxxx> <1229025794.2770.32.camel@xxxxxxxxxxxxxxxxxxxxx> <1e16a9ed0812111220h40e62ee1ma27f48c5207bc735@xxxxxxxxxxxxxx> <49417755.4050703@xxxxxxxx> <1e16a9ed0812111312p2547884cgf4020eb9ea92ddde@xxxxxxxxxxxxxx> <4941930B.2010605@xxxxxxxx> <1e16a9ed0812111427i3626b94cu7ce56550d654227a@xxxxxxxxxxxxxx> <f4527be0812120112y13e74752kbd3d17d7daa98848@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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