From: "Sven Köhler" <sven.koehler@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
David Vrabel <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: dom0 not seeing all of the assigned memory
Date: Thu, 15 Mar 2012 21:29:45 +0100 [thread overview]
Message-ID: <4F625139.9050501@gmail.com> (raw)
In-Reply-To: <1331842410.13956.40.camel@dagon.hellion.org.uk>
Am 15.03.2012 21:13, schrieb Ian Campbell:
> On Thu, 2012-03-15 at 20:07 +0000, Sven Köhler wrote:
>> Am 15.03.2012 19:54, schrieb David Vrabel:
>
>>> You need dom0_mem=max:512M
>>
>> I can't find documentation on what that does.
>
> This option is documented in the source tree, and the in tree
> documentation is published at:
> http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html
Thanks for the link. That is very useful! Is there any path that leads
from http://www.xen.org/support/documentation.html to the page above in
case I forget the URL?
However: according to that documentation dom0_mem=512M implies
dom0_mem=max:512M. Or am I wrong?
next prev parent reply other threads:[~2012-03-15 20:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 22:19 dom0 not seeing all of the assigned memory Henrik Olsson
2012-02-22 22:40 ` Henrik Olsson
2012-02-23 18:55 ` David Vrabel
2012-02-27 17:34 ` Henrik Olsson
2012-02-27 19:04 ` Roderick Colenbrander
2012-03-11 22:20 ` Sven Köhler
2012-03-15 18:33 ` Konrad Rzeszutek Wilk
2012-03-15 18:54 ` David Vrabel
2012-03-15 20:07 ` Sven Köhler
2012-03-15 20:13 ` Ian Campbell
2012-03-15 20:29 ` Sven Köhler [this message]
2012-03-15 21:55 ` Ian Campbell
2012-03-15 22:09 ` Sven Köhler
2012-03-19 11:09 ` David Vrabel
2012-03-19 12:25 ` Sven Köhler
2012-03-19 12:30 ` Fantu
2012-04-17 4:33 ` Brian Szymanski
2012-04-17 4:46 ` Brian Szymanski
2012-04-17 21:30 ` Dan Magenheimer
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=4F625139.9050501@gmail.com \
--to=sven.koehler@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--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 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.