From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43909) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5uGD-00058S-F8 for qemu-devel@nongnu.org; Fri, 19 Jun 2015 07:15:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z5uG8-0000BX-SP for qemu-devel@nongnu.org; Fri, 19 Jun 2015 07:15:01 -0400 Received: from mail.iv.net.pl ([195.191.233.10]:38122) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z5uG8-0000B0-Hz for qemu-devel@nongnu.org; Fri, 19 Jun 2015 07:14:56 -0400 Message-ID: <5583F9AC.6080200@innervision.pl> Date: Fri, 19 Jun 2015 13:14:52 +0200 From: Piotr Rybicki MIME-Version: 1.0 References: <5582DE3E.5050504@innervision.pl> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] incorrect memory size inside vm List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrey Korolyov Cc: libvir-list , "qemu-devel@nongnu.org" , Vasiliy Tolstov Hello. Actually it was my mistake. After some time using memory in guest (find /, cp bigfine, etc), res size of qemu process shrinks to expected value. Sorry for disturbing. Now i don't see any memory waste in guest and host when using 'base' memory + 'dimm' memory. Although i have one issue. When i start qemu via libvirt with 16GB mem and 1G current mem: (...) 16777216 1048576 (...) Qemu starts, and balloon can't free memmory, so guest doesn't boot (It hangs or is looped in ' virtio_balloon virtio2: Out of puff! Can't get 1 pages'). I think this is because dimm memmory is not yet onlined, and balloon already tries to shring memory in guest. Best regards Piotr Rybicki W dniu 2015-06-18 o 23:23, Andrey Korolyov pisze: >> Do You see similar results at Your side? >> >> Best regards > > Would you mind to share you argument set to an emulator? As far as I > understood you are using plain ballooning with most results from above > for which those numbers are expected. The case with 5+gig memory > consumption for deflated 1G guest looks like a bug with mixed > dimm/balloon configuration if you are tried against latest qemu, so > please describe a setup a bit more verbosely too.