From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Alexander Bienzeisler <chosi@amd.co.at>
Subject: Re: can not use all available memory
Date: Fri, 23 Nov 2012 12:47:07 +0000 [thread overview]
Message-ID: <1353674827.16973.4.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20121123124115.GW8912@reaktio.net>
On Fri, 2012-11-23 at 12:41 +0000, Pasi Kärkkäinen wrote:
> On Fri, Nov 23, 2012 at 12:33:59PM +0000, Ian Campbell wrote:
> > On Fri, 2012-11-23 at 12:28 +0000, Pasi Kärkkäinen wrote:
> > > On Fri, Nov 23, 2012 at 12:21:32PM +0000, Ian Campbell wrote:
> > > > This question belongs on xen-users.
> > > >
> > > > On Fri, 2012-11-23 at 11:35 +0000, Alexander Bienzeisler wrote:
> > > > > Hello,
> > > > >
> > > > > i just tried to add a domU with 16 gigs of ram (maxmem = 16384, memory =
> > > > > 16384) with free_memory : 28969 but got an error:
> > > > >
> > > > > libxl: error: libxl.c:3433:libxl_set_memory_target: new target 0 for
> > > > > dom0 is below the minimum threshold
> > > >
> > > > The clue is in this message -- you cannot safely balloon down a guest
> > > > (including dom0) to an arbitrarily small value relative to its initial
> > > > size. The kernel will have certain fixed datastructures etc which are
> > > > sized according to the maximum amount of RAM at start of day.
> > > >
> > > > If you were to balloon down too low then you would run out of RAM and
> > > > the OOM killer would step in and start killing stuff, so xl includes a
> > > > safety catch which prevents this.
> > > >
> > > > If you have a huge host and want a small dom0 use the dom0_mem option
> > > > and disable xl's autoballoon option or whatever the equivalent xend
> > > > option is.
> > > >
> > >
> > > I think he was already using dom0_mem. He had 28969 free in Xen as
> > > reported by "xl info".
> >
> > Then he's missed disabling autoballoon.
> >
>
> As can be seen from the other email in this thread,
> he's using dom0_mem=2048M, and he has 28GB of free memory in Xen.
>
> Why is xl trying to balloon down dom0 (and failing) for no reason?
Because autoballoon is enabled.
This has been discussed at length on the list before, please check the
archives.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-11-23 12:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 11:35 can not use all available memory Alexander Bienzeisler
2012-11-23 11:52 ` Pasi Kärkkäinen
2012-11-23 12:06 ` Alexander Bienzeisler
2012-11-23 12:21 ` Ian Campbell
2012-11-23 12:28 ` Pasi Kärkkäinen
2012-11-23 12:33 ` Ian Campbell
2012-11-23 12:41 ` Pasi Kärkkäinen
2012-11-23 12:47 ` Ian Campbell [this message]
2012-11-23 12:55 ` Pasi Kärkkäinen
2012-11-23 13:15 ` Ian Campbell
2012-11-23 13:29 ` Pasi Kärkkäinen
2012-11-23 13:33 ` Ian Campbell
2012-11-26 16:58 ` Dan Magenheimer
2012-11-26 18:25 ` Sander Eikelenboom
2012-11-26 20:20 ` Dan Magenheimer
2012-11-26 20:24 ` Pasi Kärkkäinen
2012-11-26 20:37 ` Dan Magenheimer
2012-11-26 21:32 ` Tim Deegan
2012-11-26 21:47 ` Dan Magenheimer
2012-11-27 2:52 ` William Pitcock
2012-11-27 10:52 ` Ian Campbell
2012-11-26 20:35 ` Sander Eikelenboom
2012-11-23 12:46 ` Alexander Bienzeisler
-- strict thread matches above, loose matches on Subject: below --
2012-11-23 11:38 Alexander Bienzeisler
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=1353674827.16973.4.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=chosi@amd.co.at \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).