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/
Home Products Support Community News


RE: [Xen-devel] Yet another "Why can't I see all my RAM" question

To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Yet another "Why can't I see all my RAM" question
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 26 Apr 2006 01:41:54 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 25 Apr 2006 17:42:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZow6XTYyy+HL4FTVCzxcWdyugSvQABbiYg
Thread-topic: [Xen-devel] Yet another "Why can't I see all my RAM" question
> > It would actually be fairly easy to make the Xen restriction "16GB 
> > plus a bit" so that you'd get the full 16GB of RAM even 
> with a large 
> > MMIO whole in the address space. We might implement that, 
> but using a 
> > 64b hypervisor is definitely the preferred way forward.
> OK.  The problem there is supporting all of our existing 32b 
> clients without forcing them to upgrade libs, etc (nightmare).

You can use a 64b kernel on top of a 33b distro just fine.

You also might want to see if there's a BIOS upgrade for your system.
I've never seen a memory hole anywhere near that size before (not that
its usually a particular problem). 


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>