From: Vasiliy Tolstov <v.tolstov@selfip.ru>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: libvir-list <libvir-list@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] incorrect memory size inside vm
Date: Wed, 17 Jun 2015 18:33:41 +0300 [thread overview]
Message-ID: <CACaajQsQPVjqLcoZdYj_ODXBKQzOn8tZ+LDt3mkwYhBhtstV=Q@mail.gmail.com> (raw)
In-Reply-To: <CABYiri-gNTCOAe5G0pXf6hgzna_=3VHGMK0JS-A1xQfFccDe_A@mail.gmail.com>
2015-06-17 17:09 GMT+03:00 Andrey Korolyov <andrey@xdel.ru>:
> The rest of visible memory is eaten by reserved kernel areas, for us
> this was a main reason to switch to a hotplug a couple of years ago.
> You would not be able to scale a VM by an order of magnitude with
> regular balloon mechanism without mentioned impact, unfortunately.
> Igor Mammedov posted hotplug-related patches for 2.6.32 a while ago,
> though RHEL6 never adopted them by some reason.
Hmm.. Thanks for info, from what version of kernel memory hotplug works?
--
Vasiliy Tolstov,
e-mail: v.tolstov@selfip.ru
next prev parent reply other threads:[~2015-06-17 15:34 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 [this message]
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
-- 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='CACaajQsQPVjqLcoZdYj_ODXBKQzOn8tZ+LDt3mkwYhBhtstV=Q@mail.gmail.com' \
--to=v.tolstov@selfip.ru \
--cc=andrey@xdel.ru \
--cc=libvir-list@redhat.com \
--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.