From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Memory under KVM? Date: Tue, 15 Dec 2009 12:07:55 +0200 Message-ID: <4B275FFB.9010806@redhat.com> References: <4B22BCE5.7040208@binaryfreedom.info> <200912130941.47737.tfjellstrom@shaw.ca> <4B254D45.40600@binaryfreedom.info> <200912131442.18067.tfjellstrom@shaw.ca> <4B265EB1.3070609@binaryfreedom.info> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: tfjellstrom@shaw.ca, kvm@vger.kernel.org To: rek2 Return-path: Received: from mx1.redhat.com ([209.132.183.28]:60076 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759640AbZLOKIA (ORCPT ); Tue, 15 Dec 2009 05:08:00 -0500 In-Reply-To: <4B265EB1.3070609@binaryfreedom.info> Sender: kvm-owner@vger.kernel.org List-ID: On 12/14/2009 05:50 PM, rek2 wrote: > >> VIRT includes a lot of shared memory, so it's not a very useful >> number to >> look at when trying to gauge how much memory a process is using. >> > Ok, so then what stats should we look to calculate the amount of > memory a server should have depending on how many guests we will like > to use? The -m parameter to qemu, plus some overhead. If you use ksm or ballooning or ssd swap you can overcommit, how much depends on your workload. -- error compiling committee.c: too many arguments to function