From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Re: PROBLEM: Xen ballon driver seems to be broken
	in 2.6.26
Date: Wed, 23 Jul 2008 06:35:37 -0700
Message-ID: <488733A9.5040707@goop.org>
References: <20080722181126843.00000001992@djm-pc>
	<200807231141.51212.nice@titanic.nyme.hu>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <200807231141.51212.nice@titanic.nyme.hu>
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: =?ISO-8859-15?Q?N=E9meth_Tam=E1s?= <nice@titanic.nyme.hu>
Cc: "dan.magenheimer@oracle.com" <dan.magenheimer@oracle.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, "jeremy@xensource.com" <jeremy@xensource.com>
List-Id: xen-devel@lists.xenproject.org

N=E9meth Tam=E1s wrote:
>> What is your "newest" Xen version?  If 3.2, the balloon driver fix
>> isn't there yet, but I have a bash-script workaround.  See
>> tools/xenballoond in xen-unstable.
>>    =20
>
>  The source codes of the hyperhisor and the tools were downloaded from
> xen.org a few days ago, so Xen is 3.2.1 and the dom0 kernel is
> 2.6.18.8-xen-3.2.0 (based on 2.6.18.8).
>
>  The domU kernel is 2.6.26 of course.
>
>
>
>  =20
>>> So that's consistent with the balloon driver
>>> over-aggressively shrinking
>>> the domain, until there's no memory left to do anything.  The balloon
>>> driver has no safety checks to prevent that from happening.
>>>
>>> What value are you setting the target size to?  Are you using
>>> the right
>>> units?
>>>      =20
>
> Please take a look at this:
>
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 # xm list
> Name                                        ID   Mem VCPUs      State  =
 Time(s)
> Domain-0                                     0  2048     1     r-----  =
  370.3
> u-96                                         5  1024     1     -b----  =
   14.5
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 # xm mem-set u-96 768M
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 # xm list
> Name                                        ID   Mem VCPUs      State  =
 Time(s)
> Domain-0                                     0  2048     1     r-----  =
  371.4
> u-96                                         5   768     1     -b----  =
   14.6
> carrier5:/usr/local/LOCALHOST/src/linux-2.6.26 #
>
> DomU - although being seemngly frozen - still responses for icmp echo
> requests.

Thanks, I'll have a look at it.

    J