From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andrew D. Ball" Subject: Re: Xen 3.0.4 - Ballooning Date: Mon, 08 Jan 2007 14:28:12 -0900 Message-ID: <1168298892.352.1.camel@anball> References: <45A21B32.1050705@swisscenter.com> Reply-To: aball@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <45A21B32.1050705@swisscenter.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?S=E9bastien?= RICCIO Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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=20 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=C3=A9bastien RICCIO wrote: > Hi, >=20 > Maybe it's a dumb question, but I'm actually trying to understand how=20 > the memory allocation works within Xen. >=20 > I try to give 128MB to a domU and see if it increases for example when = I=20 > "nano" a 500mb file, but the process > just get killed when it reachs the 128MB memory limit. >=20 > How do I configure the guests so they can ask for more memory until a=20 > limit is reached ? >=20 > Thanks a lot for your help. >=20 > Best regards