From: Markus Armbruster <armbru@redhat.com>
To: Sergio Lopez <slp@redhat.com>
Cc: berrange@redhat.com, ehabkost@redhat.com, mst@redhat.com,
philmd@redhat.com, groug@kaod.org, qemu-devel@nongnu.org,
marcandre.lureau@gmail.com, kraxel@redhat.com,
imammedo@redhat.com, pbonzini@redhat.com, rth@twiddle.net,
lersek@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH v11 00/15] Introduce the microvm machine type
Date: Wed, 27 Nov 2019 16:41:30 +0100 [thread overview]
Message-ID: <87imn58gyd.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20191018105315.27511-1-slp@redhat.com> (Sergio Lopez's message of "Fri, 18 Oct 2019 12:53:00 +0200")
Sergio Lopez <slp@redhat.com> writes:
> microvm is a machine type inspired by Firecracker and constructed
> after its machine model.
>
> It's a minimalist machine type without PCI nor ACPI support, designed
> for short-lived guests. microvm also establishes a baseline for
> benchmarking and optimizing both QEMU and guest operating systems,
> since it is optimized for both boot time and footprint.
I know this has been merged, but I ask anyway: got some boot time and
memory footprint measurements?
next prev parent reply other threads:[~2019-11-27 15:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 10:53 [PATCH v11 00/15] Introduce the microvm machine type Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 01/15] hw/virtio: Factorize virtio-mmio headers Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 02/15] hw/i386/pc: rename functions shared with non-PC machines Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 03/15] hw/i386/pc: fix code style issues on functions that will be moved out Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 04/15] hw/i386/pc: replace use of strtol with qemu_strtoui in x86_load_linux() Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 05/15] hw/i386/pc: avoid an assignment in if condition " Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 06/15] hw/i386/pc: remove commented out code from x86_load_linux() Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 07/15] hw/i386/pc: move shared x86 functions to x86.c and export them Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 08/15] hw/i386: split PCMachineState deriving X86MachineState from it Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 09/15] hw/i386: make x86.c independent from PCMachineState Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 10/15] fw_cfg: add "modify" functions for all types Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 11/15] hw/intc/apic: reject pic ints if isa_pic == NULL Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 12/15] roms: add microvm-bios (qboot) as binary and git submodule Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 13/15] docs/microvm.rst: document the new microvm machine type Sergio Lopez
2019-10-18 10:53 ` [PATCH v11 14/15] hw/i386: Introduce the " Sergio Lopez
2019-10-30 9:25 ` Philippe Mathieu-Daudé
2019-10-30 14:18 ` Paolo Bonzini
2019-10-18 10:53 ` [PATCH v11 15/15] MAINTAINERS: add microvm related files Sergio Lopez
2019-11-27 15:41 ` Markus Armbruster [this message]
2019-12-02 13:01 ` [PATCH v11 00/15] Introduce the microvm machine type Sergio Lopez
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=87imn58gyd.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=groug@kaod.org \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sgarzare@redhat.com \
--cc=slp@redhat.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.