From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Memory under KVM? Date: Wed, 16 Dec 2009 11:55:25 +0200 Message-ID: <4B28AE8D.6080600@redhat.com> References: <4B22BCE5.7040208@binaryfreedom.info> <200912131016.43193.tfjellstrom@shaw.ca> <4B275FB1.7000608@redhat.com> <200912151621.19082.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 mx1.redhat.com ([209.132.183.28]:31300 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754598AbZLPJz2 (ORCPT ); Wed, 16 Dec 2009 04:55:28 -0500 In-Reply-To: <200912151621.19082.tfjellstrom@shaw.ca> Sender: kvm-owner@vger.kernel.org List-ID: On 12/16/2009 01:21 AM, Thomas Fjellstrom wrote: > >>> The problem is it should be automatic. The balloon driver itself or >>> some other mechanism should be capable of noticing when it can free up >>> a bunch of guest memory. I can't be bothered to manually sit around and >>> monitor memory usage on my host so I can then go into virt-manager to >>> reduce memory to each guest. >>> >> That should be pretty easy though it will have an effect on guest >> performance. >> >> > As long as its only done after an appropriately long idle period (ie: theres > been X MB's free for a long time, give it back), I can't see it harming > performance too much. At least not more than setting ram too low when > manually (de)ballooning memory. > It depends on what your expectations are. If you have a lot of memory you might be surprised when you access an idle guest and have to wait for it to page itself back from disk. -- error compiling committee.c: too many arguments to function