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


[Xen-users] auto adjusting memory (was: system suggestion)

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] auto adjusting memory (was: system suggestion)
From: Andrew Thompson <andrewkt@xxxxxxxxxxx>
Date: Fri, 03 Jun 2005 09:16:35 -0400
Delivery-date: Fri, 03 Jun 2005 13:15:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Mark Williamson wrote:
>>IMO, the limiting factor is not CPU but RAM available to a virtual
>>machine.  it would be nice if there were some way to let memory float
>>between virtual machines based on need.  In the other hand, it may be
>>there already and I just haven't figured it out.
> It doesn't happen automatically - you'd have to use the balloon driver
> to shrink one domain and grow another one.  A feature we'd like to see
> is "auto-ballooning" where dom0 will adjust domU memory footprints
> based on their current utilisation.  This is likely to appear at some
> stage in the future...

How would you determine actual utilisation when linux likes to eat all the ram available?

Would you go by swap file usage, or something else?

(Feel free to tell me I'm under-educated about *nix systems, if necessary.)

Andrew Thompson

Attachment: andrewkt.vcf
Description: Vcard

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>