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-devel

[Xen-devel] unstable: no ballooning

To: Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] unstable: no ballooning
From: Kurt Garloff <garloff@xxxxxxx>
Date: Mon, 10 Oct 2005 12:46:39 +0200
Delivery-date: Mon, 10 Oct 2005 10:44:05 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Mail-followup-to: Kurt Garloff <garloff@xxxxxxx>, Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Organization: SUSE/Novell
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
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.

I guess some message should go over xenbus and someone should then 
write to it's balloon file. For dom0, we could do it directly in 
XendDomainInfo.setMemoryTarget(). See attached second patch. It's
a hack and certainly not the right solution.
Who should do it?

Best,
-- 
Kurt Garloff                   <kurt@xxxxxxxxxx>             [Koeln, DE]
Physics:Plasma modeling <garloff@xxxxxxxxxxxxxxxxxxx> [TU Eindhoven, NL]
Linux: SUSE Labs (Director)    <garloff@xxxxxxx>            [Novell Inc]

Attachment: xen-SrvDomain-typo.diff
Description: Text document

Attachment: xen-balloon-dom0.diff
Description: Text document

Attachment: pgp7zvQSNcBGL.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>