From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Announcing qboot, a minimal x86 firmware for QEMU
Date: Fri, 22 May 2015 12:01:36 +0100 [thread overview]
Message-ID: <20150522110136.GF14428@redhat.com> (raw)
In-Reply-To: <555DE2EF.1000509@redhat.com>
On Thu, May 21, 2015 at 03:51:43PM +0200, Paolo Bonzini wrote:
> Some of you may have heard about the "Clear Containers" initiative from
> Intel, which couple KVM with various kernel tricks to create extremely
> lightweight virtual machines. The experimental Clear Containers setup
> requires only 18-20 MB to launch a virtual machine, and needs about 60
> ms to boot.
>
> Now, as all of you probably know, "QEMU is great for running Windows or
> legacy Linux guests, but that flexibility comes at a hefty price. Not
> only does all of the emulation consume memory, it also requires some
> form of low-level firmware in the guest as well. All of this adds quite
> a bit to virtual-machine startup times (500 to 700 milliseconds is not
> unusual)".
>
> Right? In fact, it's for this reason that Clear Containers uses kvmtool
> instead of QEMU.
>
> No, wrong! In fact, reporting bad performance is pretty much the same
> as throwing down the gauntlet.
On the QEMU side of things I wonder if there is scope for taking AArch64's
'virt' machine type concept and duplicating it on all architectures. It
would be nice to have a common minimal machine type on all architectures
that discards all legacy platform stuff and focuses on the minimum needed
to run modern virtual machine optimized guest OS. People would always know
that a machine type called 'virt' was the minimal virtualization platform,
while the others all target emulation of realworld (legacy) baremetal
platforms.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-05-22 11:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 13:51 [Qemu-devel] Announcing qboot, a minimal x86 firmware for QEMU Paolo Bonzini
2015-05-21 15:48 ` Avi Kivity
2015-05-21 16:21 ` Paolo Bonzini
2015-05-21 18:28 ` Avi Kivity
2015-05-21 17:04 ` Jan Kiszka
2015-05-22 2:53 ` Yong Wang
2015-05-26 8:47 ` Stefan Hajnoczi
2015-06-05 10:42 ` Stefan Hajnoczi
2015-05-22 11:01 ` Daniel P. Berrange [this message]
2015-05-22 11:04 ` Peter Maydell
2015-05-22 11:12 ` Daniel P. Berrange
2015-05-22 11:21 ` Peter Maydell
2015-05-22 11:33 ` Daniel P. Berrange
2015-05-22 11:34 ` Gerd Hoffmann
2015-05-22 11:42 ` Markus Armbruster
2015-05-25 12:53 ` Paolo Bonzini
2015-05-26 21:25 ` Christopher Covington
2015-05-27 9:30 ` Paolo Bonzini
2015-05-27 9:36 ` Avi Kivity
2015-05-27 11:00 ` Paolo Bonzini
2015-05-27 11:54 ` Peter Maydell
2015-05-27 12:05 ` Paolo Bonzini
2015-05-27 12:50 ` Christopher Covington
2015-05-27 12:59 ` Paolo Bonzini
2015-05-27 16:24 ` Dr. David Alan Gilbert
2015-05-22 14:06 ` Gerd Hoffmann
2015-05-22 23:23 ` Kevin O'Connor
2015-05-23 3:55 ` Kevin O'Connor
2015-05-25 6:21 ` Vasiliy Tolstov
2015-05-25 15:05 ` Kevin O'Connor
2015-05-25 12:52 ` Paolo Bonzini
2015-05-25 15:11 ` Kevin O'Connor
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=20150522110136.GF14428@redhat.com \
--to=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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 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).