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: libvir-list <libvir-list@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Vasiliy Tolstov <v.tolstov@selfip.ru>
Subject: Re: [Qemu-devel] incorrect memory size inside vm
Date: Fri, 19 Jun 2015 13:14:52 +0200	[thread overview]
Message-ID: <5583F9AC.6080200@innervision.pl> (raw)
In-Reply-To: <CABYiri9OMLmwT3iyYHFU5APwE5NAqVhTA5RjSfOAA80G9eQWzQ@mail.gmail.com>

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

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.

  reply	other threads:[~2015-06-19 11:15 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 [this message]
2015-06-19 12:01                         ` Andrey Korolyov
2015-06-19 12:02                           ` Vasiliy Tolstov
2015-06-22 13:30                           ` Piotr Rybicki
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=5583F9AC.6080200@innervision.pl \
    --to=piotr.rybicki@innervision.pl \
    --cc=andrey@xdel.ru \
    --cc=libvir-list@redhat.com \
    --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).