From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58968)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <piotr.rybicki@innervision.pl>) id 1Z71oE-0003Wo-0m
	for qemu-devel@nongnu.org; Mon, 22 Jun 2015 09:30:46 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <piotr.rybicki@innervision.pl>) id 1Z71o9-00020E-QU
	for qemu-devel@nongnu.org; Mon, 22 Jun 2015 09:30:45 -0400
Received: from mail.iv.net.pl ([195.191.233.10]:59384)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <piotr.rybicki@innervision.pl>) id 1Z71o9-0001z4-CD
	for qemu-devel@nongnu.org; Mon, 22 Jun 2015 09:30:41 -0400
Message-ID: <55880DFC.20403@innervision.pl>
Date: Mon, 22 Jun 2015 15:30:36 +0200
From: Piotr Rybicki <piotr.rybicki@innervision.pl>
MIME-Version: 1.0
References: <CACaajQtxQ=oGetoM_Z3Ekt8v=5CFPzisn7L5K9uMd8a9+LKcsQ@mail.gmail.com>	<CABYiri-gNTCOAe5G0pXf6hgzna_=3VHGMK0JS-A1xQfFccDe_A@mail.gmail.com>	<CACaajQsQPVjqLcoZdYj_ODXBKQzOn8tZ+LDt3mkwYhBhtstV=Q@mail.gmail.com>	<CABYiri-yf90=xZE8pvqcPQhB_4YxbAGe3HLtRV-S+B-qOYOYWw@mail.gmail.com>	<CACaajQvmg6h3ReONVZoAo1w6YjjNBVAPVOA4FBqw2dLEA-Lprg@mail.gmail.com>	<CACaajQsZYMdsfZX+9OuCe1q+g5k9-DPCD1YzCh06xSOYx8k4Ng@mail.gmail.com>	<CABYiri919XE243-hgFicRsUxTccVdtaMyP4BjWTjr17RGUdt5Q@mail.gmail.com>	<CACaajQvcTwJmyoWuAKZwBDUPS3MhsUOAHPe=rKvAi6qZL58D0Q@mail.gmail.com>	<CABYiri9c8Yhxwr7kBAGueRYzbc6DPFbQhenFiK4QA1650U7Etg@mail.gmail.com>	<CACaajQueh8_WTC43Odqk+0sDSW5JWoAtnMoZQnnV4f2Rgdvr5Q@mail.gmail.com>	<5582DE3E.5050504@innervision.pl>	<CABYiri9OMLmwT3iyYHFU5APwE5NAqVhTA5RjSfOAA80G9eQWzQ@mail.gmail.com>	<5583F9AC.6080200@innervision.pl>
	<CABYiri-2PEFqVZHMyHeeqZx-rZFYTmQHF+O-Xp2drfdy8GbFMQ@mail.gmail.com>
In-Reply-To: <CABYiri-2PEFqVZHMyHeeqZx-rZFYTmQHF+O-Xp2drfdy8GbFMQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] incorrect memory size inside vm
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Vasiliy Tolstov <v.tolstov@selfip.ru>



W dniu 2015-06-19 o 14:01, Andrey Korolyov pisze:
> On Fri, Jun 19, 2015 at 2:14 PM, Piotr Rybicki
> <piotr.rybicki@innervision.pl> wrote:
>> 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:
>> (...)
>>    <memory unit='KiB'>16777216</memory>
>>    <currentMemory unit='KiB'>1048576</currentMemory>
>> (...)
>>
>> 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
>>
>>
> - libvir@
>
> Please don`t top-post in technical mailing lists. Do you have a
> crashkernel-reserved area there in the boot arguments? What
> distro/guest kernel are running in this guest and what is dimm
> configuration?
>

Hi.

No, I don't have a crashkernel reserved area.

But I've solved my problem. I load virtio-balloon device as a module 
(previously it was kernel built-in), and everything is working as expected.

Thank You for Your attention.

Best regards
Piotr Rybicki