From: "Denis V. Lunev" <den@openvz.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] guest kernel in the host RAM
Date: Fri, 18 Dec 2015 19:28:51 +0300 [thread overview]
Message-ID: <56743443.5000907@openvz.org> (raw)
In-Reply-To: <567000B8.2070300@redhat.com>
On 12/15/2015 02:59 PM, Paolo Bonzini wrote:
>
> On 15/12/2015 12:27, Denis V. Lunev wrote:
>> The idea is that we could boot with the uncompressed Linux
>> kernel in the guest which serves 2 purposes:
>> - faster boot time as per Intel opinion
>> - memory savings
>>
>> Uncompressed kernel image could be the same for several
>> guests and thus memory pages for the kernel could be the
>> same, which saves a bit of RAM :)
>>
>> At the moment neither BIOS support this in full: nor SeaBIOS,
>> nor OVMF, nor QBoot.
>>
>> From our point of view QBoot is an ideal candidate for this.
> QBoot is not meant for use in production; SeaBIOS actually is just as
> fast if you configure it right.
>
>> Do you have any opinion for the topic?
> I honestly don't like the idea. Linux patches itself a lot, which
> makes the memory savings minimal (if they exist at all). What is the
> decompression time for a kernel that is compressed with LZO?
>
> Paolo
It seems that you are perfectly correct here!
With large pages enabled (and preferred 2 Mb pages mode)
we will have exactly zero bonus.
Thank you for saving a lot of time and efforts :)))
Den
next prev parent reply other threads:[~2015-12-18 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566EE582.2070408@virtuozzo.com>
2015-12-15 11:27 ` [Qemu-devel] guest kernel in the host RAM Denis V. Lunev
2015-12-15 11:59 ` Paolo Bonzini
2015-12-18 16:28 ` Denis V. Lunev [this message]
2015-12-18 18:03 ` Paolo Bonzini
2015-12-16 3:18 ` Stefan Hajnoczi
2015-12-16 9:56 ` Miao Yan
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=56743443.5000907@openvz.org \
--to=den@openvz.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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.