From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Xen Ballon Bug in 2.6.27-git11
Date: Fri, 25 Jul 2008 07:49:24 -0700
Message-ID: <4889E7F4.6030907@goop.org>
References: <48886E71.6040306@work.de> <488895BF.4000203@goop.org>
	<4889A09B.4050307@work.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4889A09B.4050307@work.de>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "viets@work.de" <viets@work.de>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

viets@work.de wrote:
> Hello,
>
> with your patch I didn't get any error, but if I start a machine with
> 128 MB RAM and increase it per xm mem-set up to 256MB, neither top or
> cat /proc/meminfo shows the new memory...
>   

Yes, that's expected for now.  Currently the balloon driver can only 
contract a domain, and re-expand it back to its original size.  I have 
code to do expansion too, but it needs some work before being mergable.

    J