From: "Sébastien RICCIO" <sr@swisscenter.com>
To: aball@linux.vnet.ibm.com
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen 3.0.4 - Ballooning
Date: Tue, 09 Jan 2007 11:29:52 +0100 [thread overview]
Message-ID: <45A36EA0.4090704@swisscenter.com> (raw)
In-Reply-To: <1168298892.352.1.camel@anball>
Hi Andrew,
Thank you a lot for your answer. I will try to play with this a little.
Best regards.
--
Sébastien Riccio
SwissCenter / OpenBusiness SA
sr@openbusiness.com
Andrew D. Ball a écrit :
> Not such a dumb question. As far as I know, memory ballooning is only
> done from the control partition (dom0) nowadays, explicitly.
>
> It would be nice for something inside of a domU's kernel or userspace to
> watch
> some metric and then ask nicely for more memory if needed. Paravirtual
> drivers
> can do this for sure, but I haven't poked around enough to know which
> available
> ones do and how to trigger it.
>
> Peace.
> Andrew
>
> On Mon, 2007-01-08 at 11:21 +0100, Sébastien RICCIO wrote:
>
>> Hi,
>>
>> Maybe it's a dumb question, but I'm actually trying to understand how
>> the memory allocation works within Xen.
>>
>> I try to give 128MB to a domU and see if it increases for example when I
>> "nano" a 500mb file, but the process
>> just get killed when it reachs the 128MB memory limit.
>>
>> How do I configure the guests so they can ask for more memory until a
>> limit is reached ?
>>
>> Thanks a lot for your help.
>>
>> Best regards
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2007-01-09 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 10:21 Xen 3.0.4 - Ballooning Sébastien RICCIO
2007-01-08 23:28 ` Andrew D. Ball
2007-01-09 10:29 ` Sébastien RICCIO [this message]
2007-03-23 3:31 ` question about gmfn_to_mfn() tgh
2007-03-23 6:56 ` Guy Zana
2007-03-23 10:22 ` Keir Fraser
2007-03-26 1:09 ` tgh
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=45A36EA0.4090704@swisscenter.com \
--to=sr@swisscenter.com \
--cc=aball@linux.vnet.ibm.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.