WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] understanding memory hot-plug in a paravitual domU

To: jordi@xxxxxxxxx
Subject: Re: [Xen-users] understanding memory hot-plug in a paravitual domU
From: Kyle Lexmond <kyl191@xxxxxxxxxx>
Date: Fri, 18 Nov 2011 18:47:36 +0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Nov 2011 02:49:38 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyl191.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4Z2mMOvKmTOsvOBQJKrNsY/k4QmCpFNw9GhDxhoRMnM=; b=XnpzYYHUgqn1C/ok3j8tQYLzoxfKMpmJciV1HuZ/bu0THP5cnV0NadVBlj56cfPQX7 vEfsrksXbldCVNRICe+PzoDiBuwmzVJNLH9NXMsq8m3gbB874N4puf6E7b118bqqdoAv 6MxqgPUcZvOZF1Dxmyw3xlybeCp0P+SpIKw7k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4EC4C279.6050700@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4EC3B978.2070607@xxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01EDFCF0@trantor> <4EC4C279.6050700@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
Everything that I've read said that you can't balloon the memory
beyond the maximum you specified in the config file when you created
the domain. (eg.
http://www.centos.org/docs/5/html/Virtualization-en-US/virt-task-xm-create-manage-doms.html#id2645186)

So, no, based on the docs, the behaviour that you're seeing is
expected, and, no, you can't balloon higher than the initial memory
value.

Strange that xm mem-max isn't giving errors though.

...
> **********
> # xm mem-max server 4096
> # xm mem-set server 4096
> **********
>
>
> can i suppose then that this should work?
>
> the thing is that xen doesn't complain, but both 'xen top' and the machine
> itself don't seem to show any increase in the memory.
>
> However, it works when setting a lower value.
>
> For example, I can create 'server' with 2048 and then go down to 1024 and
> then to 2048 again, but never to a higher value. So... i guess that
> mem-hotplug works because I can go down and up, but It can never go up
> higher than the initial memory value.
>
> that's why yesterday I was asking if that's is even possible,

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users