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/
Home Products Support Community News


Re: [Xen-devel] unstable: no ballooning

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] unstable: no ballooning
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Wed, 12 Oct 2005 14:06:13 +0100
Cc: Kurt Garloff <garloff@xxxxxxx>
Delivery-date: Wed, 12 Oct 2005 13:03:34 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051010104639.GA18307@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20051010104639.GA18307@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Oct 10, 2005 at 12:46:39PM +0200, Kurt Garloff wrote:

> Hi,
> when using xm mem-set on current (7278) unstable, you'll see
> [2005-10-10 10:25:51 xend] ERROR (SrvBase:87) Request mem_target_set failed.
> Traceback (most recent call last):
>   File "/usr/lib/python2.4/site-packages/xen/web/SrvBase.py", line 85, in 
> perform
>     return op_method(op, req)
>   File "/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomain.py", line 
> 132, in op_mem_target_set
>     return self.call(self.dom.setMemoryTarget
> TypeError: unsubscriptable object
> in xend.log.
> The fix is trivial, a comma is missing, see (first) attached patch.
> HOWEVER, this still does not make balllooning work.
> Nobody ever writes to /proc/xen/balloon.

Kurt, could you please retest with today's unstable?  I have put your first
patch in (thanks for that) and we have made some changes to the xenstore watch
interface recently, so that may help with the second problem.

The idea is that the memory/target value gets written by Xend, and and the
balloon driver holds a watch on that value in the store.  When the watch
fires, the balloon driver should respond by setting the new target

Watches have been broken in various ways over the last few days, and the bugs
we know about there have now been fixed, so I would be interested to know
whether your bug has been fixed in the process.



Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>