From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Very high memory usage with KVM Date: Sun, 26 Jul 2009 19:19:39 +0300 Message-ID: <4A6C821B.5020007@redhat.com> References: <20090725174340.GA21733@defiant.freesoftware.org> <4A6C3EAD.9040303@redhat.com> <20090726145603.GD31411@defiant.freesoftware.org> <4A6C721F.8030702@redhat.com> <20090726155012.GE31411@defiant.freesoftware.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: dbareiro@gmx.net, KVM General Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35600 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753713AbZGZQPQ (ORCPT ); Sun, 26 Jul 2009 12:15:16 -0400 In-Reply-To: <20090726155012.GE31411@defiant.freesoftware.org> Sender: kvm-owner@vger.kernel.org List-ID: On 07/26/2009 06:50 PM, Daniel Bareiro wrote: >> kvm memory management with pre 2.6.27 host kernels is pretty weak. >> Using a newer host kernel (and newer kvm) may solve this problem. >> > > Initially I am going to see how it improves the situation upgrading to > KVM-84 of backports of Hardy Heron, since at the moment last kernel > available for Hardy is the one I has commented. > > I would like to know if the newest versions of KVM published in the > official site of the project solve a bug recently reported in Ubuntu > Launchpad [1]. Also I was observing errors of type 'to swapper Not > tainted' or 'java Not tainted' in the VM (aps2, with a high rate of I/O) > and that I've commented in a previous message sent to the list [2]. I > would want to know if you could indicate to me if this can be due to KVM > bug that would be solved in a later version. > > My guess is that it is due to poor swapping with pre-2.6.27 hosts. 15 GB used out of 16GB total is just 6% reserve, which may be a bit too low. With a 2.6.27 host some small amount of memory would be swapped out, before that you'd see thrashing. Another way to check is to drop one guest (or reduce total memory needed by 1GB) and see if you get the same results or if things improve. -- error compiling committee.c: too many arguments to function