From: Piotr Rybicki <piotr.rybicki@innervision.pl>
To: andrey@xdel.ru
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] incorrect memory size inside vm
Date: Tue, 23 Jun 2015 14:32:20 +0200 [thread overview]
Message-ID: <558951D4.1010603@innervision.pl> (raw)
> Thanks Piotr, the lack of the host-side memory shrinkage after balloon
> deflation is interesting anyway, hopefully you may share guest` dmesg
> bits from compiled-in balloon to check visible signs of the issue
It is really hard to see dmesg output via vnc console, when kernel is sending so many messages looped :(
> (balloon should be initialized *before* DIMMs are being onlined, so
> the behavior of the balloon itself it not clear at least for me).
Why balloon should be initialized before DIMMs onlined?
DIMMS are onlined as soon as udev starts (i have udev rule to online mem, cpu), so system has to start init process. I don't see any option to online DIMMs before booting reaches init process.
With balloon compiled-in, it starts to shrink memmory (for example to shrink 8GB, when 1GB 'base' mem is defined, and 10GB in DIMMs), when there is only 1GB 'base' memory. This leads to problem
With balloon loaded as a module, shrinking starts after init has begun (because system has to at least mount filesystem where balloon module is placed to load)
Well, i can't proove this with dmesg, but with balloon as module - system is booting and working as expected. With balloon compiled-in - system does not boot saying there is no free mem for balloon to shrink it.
Best regards
Piotr Rybicki
next reply other threads:[~2015-06-23 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 12:32 Piotr Rybicki [this message]
2015-06-23 18:59 ` [Qemu-devel] incorrect memory size inside vm Andrey Korolyov
2015-06-23 22:10 ` Piotr Rybicki
-- strict thread matches above, loose matches on Subject: below --
2015-06-17 13:35 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
2015-06-22 15:58 ` Andrey Korolyov
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=558951D4.1010603@innervision.pl \
--to=piotr.rybicki@innervision.pl \
--cc=andrey@xdel.ru \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.