From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Nick Pegg <npegg@linode.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 32-bit PV guests and 168 GB boundary
Date: Mon, 15 Apr 2013 15:51:23 +0100 [thread overview]
Message-ID: <516C13EB.4050209@citrix.com> (raw)
In-Reply-To: <516C0CD1.90403@linode.com>
On 15/04/13 15:21, Nick Pegg wrote:
> 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
This is because of the amount of the Xen m2p table mapped into 32bit
kernel space, between 0xf5800000 and 0xffffffff. PV guests require the
m2p table to perform paravirtualised memory management. This is a
fundamental limit of 32bit PV guests.
~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-15 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 14:21 32-bit PV guests and 168 GB boundary Nick Pegg
2013-04-15 14:48 ` Jan Beulich
2013-04-15 14:51 ` Andrew Cooper [this message]
2013-04-15 14:52 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516C13EB.4050209@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=npegg@linode.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.