From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: automatic memory ballooning? Date: Sun, 16 Aug 2009 17:30:59 +0300 Message-ID: <4A881823.2040500@redhat.com> References: <200908160355.46652.tfjellstrom@shaw.ca> <4A87EE43.6090109@redhat.com> <200908160818.46436.tfjellstrom@shaw.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: tfjellstrom@shaw.ca Return-path: Received: from mx2.redhat.com ([66.187.237.31]:40589 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750907AbZHPObA (ORCPT ); Sun, 16 Aug 2009 10:31:00 -0400 In-Reply-To: <200908160818.46436.tfjellstrom@shaw.ca> Sender: kvm-owner@vger.kernel.org List-ID: On 08/16/2009 05:18 PM, Thomas Fjellstrom wrote: > On Sun August 16 2009, Avi Kivity wrote: > >> On 08/16/2009 12:55 PM, Thomas Fjellstrom wrote: >> >>> I'm wondering if kvm supports automatic memory ballooning. I've had a kvm >>> guest running for a couple days, and the balloon driver was loaded, and I >>> could manually change the amount of ram it had allocated in the console, >>> but it never seemed to change automatically. >>> >>> Is there any support for that? >>> >> That would be part of a management application. qemu only knows about >> the guest it controls, while ballooning needs a global view of the system. >> > All a single guest needs to do is only use as much ram as it needs at any > given time (up to the max allocated). So if the guest hasn't used much ram in > a given time frame, "free" the free ram from the host, and only reallocate > when needed. It doesn't _need_ a management application, just happens to be > the way people do it. > Well, for a single guest you are correct, but this is better solved generically for multiple guests. -- error compiling committee.c: too many arguments to function