qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pankaj Gupta <pagupta@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: ehabkost@redhat.com, Sergio Lopez <slp@redhat.com>,
	mst@redhat.com, philmd@redhat.com, mtosatti@redhat.com,
	qemu-devel@nongnu.org, kraxel@redhat.com, kvm@vger.kernel.org,
	imammedo@redhat.com, pbonzini@redhat.com, lersek@redhat.com,
	rth@twiddle.net
Subject: Re: [PATCH v4 0/8] Introduce the microvm machine type
Date: Wed, 25 Sep 2019 04:37:42 -0400 (EDT)	[thread overview]
Message-ID: <1911476948.2948619.1569400662114.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <3162a686-90c8-9ace-0258-37464390ca45@redhat.com>


> >>> Microvm is a machine type inspired by both NEMU and Firecracker, and
> >>> constructed after the machine model implemented by the latter.
> >>>
> >>> It's main purpose is providing users a minimalist machine type free
> >>> from the burden of legacy compatibility, serving as a stepping stone
> >>> for future projects aiming at improving boot times, reducing the
> >>> attack surface and slimming down QEMU's footprint.
> >>>
> >>> The microvm machine type supports the following devices:
> >>>
> >>>  - ISA bus
> >>>  - i8259 PIC
> >>>  - LAPIC (implicit if using KVM)
> >>>  - IOAPIC (defaults to kernel_irqchip_split = true)
> >>>  - i8254 PIT
> >>>  - MC146818 RTC (optional)
> >>>  - kvmclock (if using KVM)
> >>>  - fw_cfg
> >>>  - One ISA serial port (optional)
> >>>  - Up to eight virtio-mmio devices (configured by the user)
> >>
> >> So I assume also no ACPI (CPU/memory hotplug), correct?
> > 
> > Correct.
> > 
> >> @Pankaj, I think it would make sense to make virtio-pmem play with
> >> virtio-mmio/microvm.
> > 
> > That would be great. I'm also looking forward for virtio-mem (and an
> > hypothetical virtio-cpu) to eventually gain hotplug capabilities in
> > microvm.
> 
> @Pankaj, do you have time to look into the virtio-pmem thingy? I guess
> the virtio-mmio rapper shouldn't be too hard (very similar to the
> virtio-pci wrapper - luckily I insisted to make it work independently
> from PCI BARs and ACPI slots ;) ). The microvm bits would be properly
> setting up device memory and wiring up the hotplug handlers, similar as
> done in the other PC machine types (maybe that comes for free?).

Yes, I can look at.

> 
> virtio-pmem will allow (in read-only mode) to place the rootfs on a fake
> NVDIMM, as done e.g., in kata containers. We might have to include the
> virtio-pmem kernel module in the initramfs, shouldn't  be too hard. Not
> sure what else we'll need to make virtio-pmem get used as a rootfs.

Sure, will work on it.

Thanks,
Pankaj

> 
> > 
> > Thanks,
> > Sergio.
> > 
> 
> 
> --
> 
> Thanks,
> 
> David / dhildenb
> 
> 


  reply	other threads:[~2019-09-25  8:38 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 12:44 [PATCH v4 0/8] Introduce the microvm machine type Sergio Lopez
2019-09-24 12:44 ` [PATCH v4 1/8] hw/i386: Factorize PVH related functions Sergio Lopez
2019-09-24 13:18   ` Philippe Mathieu-Daudé
2019-09-25  6:03     ` Sergio Lopez
2019-09-25  8:36   ` Stefano Garzarella
2019-09-25  9:00     ` Sergio Lopez
2019-09-25  9:29       ` Stefano Garzarella
2019-09-24 12:44 ` [PATCH v4 2/8] hw/i386: Factorize e820 " Sergio Lopez
2019-09-24 13:20   ` Philippe Mathieu-Daudé
2019-09-24 14:12     ` Sergio Lopez
2019-09-24 12:44 ` [PATCH v4 3/8] hw/virtio: Factorize virtio-mmio headers Sergio Lopez
2019-09-24 12:44 ` [PATCH v4 4/8] hw/i386: split PCMachineState deriving X86MachineState from it Sergio Lopez
2019-09-24 13:40   ` Philippe Mathieu-Daudé
2019-09-25 15:39     ` Philippe Mathieu-Daudé
2019-09-24 12:44 ` [PATCH v4 5/8] fw_cfg: add "modify" functions for all types Sergio Lopez
2019-09-24 12:44 ` [PATCH v4 6/8] roms: add microvm-bios (qboot) as binary and git submodule Sergio Lopez
2019-09-24 13:31   ` Philippe Mathieu-Daudé
2019-09-25  6:09     ` Sergio Lopez
2019-09-24 12:44 ` [PATCH v4 7/8] docs/microvm.txt: document the new microvm machine type Sergio Lopez
2019-09-24 13:10   ` Paolo Bonzini
2019-09-25  5:49     ` Sergio Lopez
2019-09-25  7:57       ` Paolo Bonzini
2019-09-25  8:40         ` Sergio Lopez
2019-09-25  9:22           ` Paolo Bonzini
2019-09-25 11:04             ` Sergio Lopez
2019-09-25 11:20               ` Paolo Bonzini
2019-09-25 15:04     ` Sergio Lopez
2019-09-25 16:46       ` Paolo Bonzini
2019-09-26  6:23         ` Sergio Lopez
2019-09-26  8:58           ` Paolo Bonzini
2019-09-26 10:16             ` Sergio Lopez
2019-09-26 10:21               ` Paolo Bonzini
2019-09-26 12:12                 ` Sergio Lopez
2019-09-25  5:06   ` Gerd Hoffmann
2019-09-25  7:33     ` Sergio Lopez
2019-09-25  8:51       ` Gerd Hoffmann
2019-09-24 12:44 ` [PATCH v4 8/8] hw/i386: Introduce the " Sergio Lopez
2019-09-24 13:12   ` Paolo Bonzini
2019-09-24 13:24     ` Michael S. Tsirkin
2019-09-24 13:34       ` Paolo Bonzini
2019-09-25  5:53     ` Sergio Lopez
2019-09-24 13:28   ` Michael S. Tsirkin
2019-09-25  5:59     ` Sergio Lopez
2019-10-01  8:56       ` Sergio Lopez
2019-09-25 15:40   ` Philippe Mathieu-Daudé
2019-09-26  6:34     ` Sergio Lopez
2019-09-26  8:59       ` Paolo Bonzini
2019-09-24 13:57 ` [PATCH v4 0/8] " Peter Maydell
2019-09-25  5:51   ` Sergio Lopez
2019-09-25 11:33     ` Philippe Mathieu-Daudé
2019-09-25 12:39       ` Peter Maydell
2019-09-25  7:41 ` David Hildenbrand
2019-09-25  7:58   ` Pankaj Gupta
2019-09-25  8:10   ` Sergio Lopez
2019-09-25  8:16     ` David Hildenbrand
2019-09-25  8:37       ` Pankaj Gupta [this message]
2019-09-25  8:26     ` Paolo Bonzini
2019-09-25  8:42       ` Sergio Lopez
2019-09-25  8:44       ` David Hildenbrand
2019-09-25 10:19         ` when to use virtio (was Re: [PATCH v4 0/8] Introduce the microvm machine type) Paolo Bonzini
2019-09-25 10:50           ` David Hildenbrand
2019-09-25 11:24             ` Paolo Bonzini
2019-09-25 11:32               ` David Hildenbrand
2019-09-25  9:12       ` [PATCH v4 0/8] Introduce the microvm machine type Gerd Hoffmann
2019-09-25  9:29         ` Paolo Bonzini
2019-09-25  9:47         ` David Hildenbrand
2019-09-26  7:48 ` Christian Borntraeger
2019-09-26  8:22   ` 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=1911476948.2948619.1569400662114.JavaMail.zimbra@redhat.com \
    --to=pagupta@redhat.com \
    --cc=david@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lersek@redhat.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --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 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).