qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Rybicki <piotr.rybicki@innervision.pl>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Vasiliy Tolstov <v.tolstov@selfip.ru>
Subject: Re: [Qemu-devel] incorrect memory size inside vm
Date: Mon, 22 Jun 2015 15:30:36 +0200	[thread overview]
Message-ID: <55880DFC.20403@innervision.pl> (raw)
In-Reply-To: <CABYiri-2PEFqVZHMyHeeqZx-rZFYTmQHF+O-Xp2drfdy8GbFMQ@mail.gmail.com>



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

  parent reply	other threads:[~2015-06-22 13:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 13:35 [Qemu-devel] incorrect memory size inside vm Vasiliy Tolstov
2015-06-17 14:09 ` Andrey Korolyov
2015-06-17 15:33   ` Vasiliy Tolstov
2015-06-17 15:38     ` Andrey Korolyov
2015-06-17 16:26       ` Vasiliy Tolstov
2015-06-17 21:21         ` Vasiliy Tolstov
2015-06-17 22:40           ` Andrey Korolyov
2015-06-17 22:44             ` Vasiliy Tolstov
2015-06-17 22:52               ` Andrey Korolyov
2015-06-17 22:57                 ` Vasiliy Tolstov
2015-06-18 15:05                   ` Piotr Rybicki
2015-06-18 21:23                     ` Andrey Korolyov
2015-06-19 11:14                       ` Piotr Rybicki
2015-06-19 12:01                         ` Andrey Korolyov
2015-06-19 12:02                           ` Vasiliy Tolstov
2015-06-22 13:30                           ` Piotr Rybicki [this message]
2015-06-22 15:58                             ` Andrey Korolyov
  -- strict thread matches above, loose matches on Subject: below --
2015-06-23 12:32 Piotr Rybicki
2015-06-23 18:59 ` Andrey Korolyov
2015-06-23 22:10   ` Piotr Rybicki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55880DFC.20403@innervision.pl \
    --to=piotr.rybicki@innervision.pl \
    --cc=andrey@xdel.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=v.tolstov@selfip.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).