qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Yang Zhong <yang.zhong@intel.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] About the light VM solution!
Date: Tue, 5 Dec 2017 16:31:09 +0000	[thread overview]
Message-ID: <20171205163109.GC6712@stefanha-x1.localdomain> (raw)
In-Reply-To: <876e5376-d729-72d7-3c04-3c6f52b745de@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]

On Tue, Dec 05, 2017 at 03:00:10PM +0100, Paolo Bonzini wrote:
> On 05/12/2017 14:47, Stefan Hajnoczi wrote:
> > On Tue, Dec 5, 2017 at 1:35 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >> On 05/12/2017 13:06, Stefan Hajnoczi wrote:
> >>> On Tue, Dec 05, 2017 at 02:33:13PM +0800, Yang Zhong wrote:
> >>>> As you know, AWS has decided to switch to KVM in their clouds. This news make almost all
> >>>> china CSPs(clouds service provider) pay more attention on KVM/Qemu, especially light VM
> >>>> solution.
> >>>>
> >>>> Below are intel solution for light VM, qemu-lite.
> >>>> http://events.linuxfoundation.org/sites/events/files/slides/Light%20weight%20virtualization%20with%20QEMU%26KVM_0.pdf
> >>>>
> >>>> My question is whether community has some plan to implement light VM or alternative solutions? If no, whether our
> >>>> qemu-lite solution is suitable for upstream again? Many thanks!
> >>>
> >>> What caused a lot of discussion and held back progress was the approach
> >>> that was taken.  The basic philosophy seems to be bypassing or
> >>> special-casing components in order to avoid slow operations.  This
> >>> requires special QEMU, firmware, and/or guest kernel binaries and causes
> >>> extra work for the management stack, distributions, and testers.
> >>
> >> I think having a special firmware (be it qboot or a special-purpose
> >> SeaBIOS) is acceptable.
> > 
> > The work Marc Mari Barcelo did in 2015 showed that SeaBIOS can boot
> > guests quickly.  The guest kernel was entered in <35 milliseconds
> > IIRC.  Why is special firmware necessary?
> 
> I thought that wasn't the "conventional" SeaBIOS, but rather one with
> reduced configuration options, but I may be remembering wrong.

Marc didn't spend much time on optimizing SeaBIOS, he used the build
options that were suggested.  An extra flag can be added in
qemu_preinit() to skip slow init that's unnecessary on optimized
machines.  That would allow a single SeaBIOS binary to run both full and
lite systems.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-12-05 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  6:33 [Qemu-devel] About the light VM solution! Yang Zhong
2017-12-05 12:06 ` Stefan Hajnoczi
2017-12-05 13:35   ` Paolo Bonzini
2017-12-05 13:47     ` Stefan Hajnoczi
2017-12-05 14:00       ` Paolo Bonzini
2017-12-05 16:31         ` Stefan Hajnoczi [this message]
2017-12-06  9:21           ` Gonglei (Arei)
2017-12-06 15:09             ` Stefan Hajnoczi
2017-12-07  0:49               ` Gonglei (Arei)
2017-12-06 15:11     ` Stefan Hajnoczi
2017-12-08 11:29       ` Yang Zhong
2017-12-07 12:03 ` Richard W.M. Jones

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=20171205163109.GC6712@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=yang.zhong@intel.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 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).