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] Status of xenballoond?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Status of xenballoond?
From: "Fajar A. Nugraha" <list@xxxxxxxxx>
Date: Mon, 21 Feb 2011 10:35:41 +0700
Delivery-date: Sun, 20 Feb 2011 19:36:41 -0800
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Is xenballoond still maintained?

http://lxr.xensource.com/lxr/source/tools/xenballoon/xenballoond still
use "echo $tgtbytes > /proc/xen/balloon", while /proc/xen/balloon does
not exists in pv_ops kernel. There's
/sys/devices/system/xen_memory/xen_memory0/target_kb , which seems to
work as expected, so it might be a simple matter of adding a test to
choose which file to write memory target to.

Also, when writing a number lower than initial value to
/sys/devices/system/xen_memory/xen_memory0/target_kb, "xm list" on
dom0 still shows old memory value, but "xm info" correctly shows some
memory freed. This is different with "xm mem-set" from dom0, which
correctly updates both values.

-- 
Fajar

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

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