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-users] Ballooning and Free memory in xm info

To: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Subject: Re: [Xen-users] Ballooning and Free memory in xm info
From: Stefan de Konink <skinkie@xxxxxxxxx>
Date: Sat, 19 Jul 2008 19:07:50 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 19 Jul 2008 10:08:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200807191736.25300.mark.williamson@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <48820E32.9080201@xxxxxxxxx> <200807191723.50486.mark.williamson@xxxxxxxxxxxx> <488216B6.8070105@xxxxxxxxx> <200807191736.25300.mark.williamson@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080519)
Mark Williamson schreef:
I'm currently creating an cluster economy

Ah, a nice plan.

It is based around my current REST http-interface to libvirt, so an avahi request is put on the network (offer), and the available cluster nodes can give their tender, lowest will get it. For now I keep it simple; that means no exact migration costs, just the cost of overcommitting with respect to free memory.

Our setup require this to work before ip address allocation... but I suppose it would work for anyone with just a switched network as a charm.

Make sure to disable autoballooning so you don't confuse things by accidentally shrinking dom0 further :-)

Will I get away with dom0_mem or should I pass dom0-min-mem=0 in the xendconfig? Or is there a cmdline param that disables ballooning?


Xen-users mailing list