From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Re: [kvm] Re: [kvm] Re: [kvm] Re: Questions about duplicate memory work Date: Sun, 02 Oct 2011 10:56:13 +0200 Message-ID: <4E88272D.5050709@redhat.com> References: <20110926071803.GE18099@stodi.digitalkingdom.org> <20110927073842.GY18099@stodi.digitalkingdom.org> <20110927084843.GB28218@stodi.digitalkingdom.org> <20110927090000.GC28218@stodi.digitalkingdom.org> <4E819C29.9040000@redhat.com> <20110929001105.GG11528@stodi.digitalkingdom.org> <20110929001447.GI11528@stodi.digitalkingdom.org> <20110929172243.GA7202@amt.cnet> <20110929184603.GR11528@stodi.digitalkingdom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , Emmanuel Noobadmin , kvm@vger.kernel.org, Andrea Arcangeli To: Robin Lee Powell Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28008 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751675Ab1JBI4V (ORCPT ); Sun, 2 Oct 2011 04:56:21 -0400 In-Reply-To: <20110929184603.GR11528@stodi.digitalkingdom.org> Sender: kvm-owner@vger.kernel.org List-ID: On 09/29/2011 09:46 PM, Robin Lee Powell wrote: > On Thu, Sep 29, 2011 at 02:22:43PM -0300, Marcelo Tosatti wrote: > > On Wed, Sep 28, 2011 at 05:14:47PM -0700, Robin Lee Powell wrote: > > > > > Please post the contents of /proc/meminfo and /proc/zoneinfo > > > > > when this is happening. > > > > > > > > I just noticed that the amount of RAM the VMs had in VIRT > > > > added up to considerably more than the host's actual RAM; > > > > hard_limit is now on. So I may not be able to replicate this. > > > > :) > > > > > > Or not; even with hard_limit the VIRT value goes to hundreds of > > > MiB more than the limit. Is that expected? > > > > Yes, VIRT field refers to total memory mapped by the process, not > > paged-in memory, which is indicated by the RES field. > > Yes, I'm aware of that; that isn't relevant to my question. > > I would expect the *total* memory requested by a VM to never go over > the hard_limit value set in the XML file. I mean, isn't that what > the hard_limit *means*? If not, what does it mean? > > VIRT memory includes both guest memory, and memory reserved (usually not used) by qemu. Don't read too much into it. -- error compiling committee.c: too many arguments to function