From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nick Pegg <npegg@linode.com>
Subject: 32-bit PV guests and 168 GB boundary
Date: Mon, 15 Apr 2013 10:21:05 -0400
Message-ID: <516C0CD1.90403@linode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Hello,

I've recently ran into a problem on a physical machine with a large
amount of memory where 32-bit PV guests would refuse to boot with this
error message:

xm create: Error: (4, 'Out of memory', "panic: xc_dom_boot.c:159:
xc_dom_boot_mem_init: can't allocate low memory for domain")

We discovered that there's a boundary where 32-bit PV guests can't be
allocated memory above 168GB, along with the work-around config option
to reserve memory for these guests (total_available_memory in
xend-config.sxp).

Could someone clarify why this is a restriction? Is this some sort of
hardware limitation?


Thanks,
Nick