Domino
October 30, 2026, 10:47am
1
Hi Stéphane
Thanks for Incus. It already covers system containers, OCI containers and full VMs under one API.
Would you consider adding micro-VMs (Firecracker, Cloud Hypervisor, or QEMU’s microvm machine type) as a fourth instance type?
The benefits would be:
much faster boot and a lower memory footprint than full VMs
VM-level isolation for OCI workloads, which suits CI runners and untrusted code
the same Incus UX (profiles, networks, storage, clustering)
QEMU microvm looks like the easiest first step, since Incus already drives QEMU.
Is this something that fits the project’s scope? I’m happy to help test or prototype
bensmrs
(Benjamin Somers)
October 30, 2026, 11:04am
2
No. This has been discussed over and over; here are a few recent discussion threads.
A fun project: microvms with Incus
I saw this blog post for microvms in Proxmox , and it got me thinking, “Couldn’t I do the same in Incus?” So I decided to mess around and see if I could end up with a profile I could make, to make use of qemu’s microvm feature in Incus. It turns out, it’s entirely possible to get it working, and it works better than I could have imagined.
What’s a microvm?
Here is QEMU’s own description:
microvm is a machine type inspired by Firecracker and constructed after …
opened 05:35PM - 29 Sep 25 UTC
closed 05:42PM - 29 Sep 25 UTC
### Is there an existing issue for this?
- [x] There is no existing issue for t… his feature
Hi Incus team,
First, thank you for all the great work on Incus — it’s impressive how it already provides a unified way to run LXC containers, OCI containers, and virtual machines.
I’d like to suggest exploring the possibility of adding MicroVM support to Incus, using a new --microvm option. Backends like Firecracker or Cloud Hypervisor could provide this functionality.
Why this could be interesting
MicroVMs are designed to be extremely lightweight and secure, with a minimal device model and very fast boot times.
They could fill the gap between containers and full VMs — stronger isolation than LXC/OCI containers, but much lighter and faster than traditional QEMU VMs.
This would allow Incus to cover an even broader set of use cases, from multi-tenant hosting to CI/CD pipelines, serverless platforms, or edge workloads where lifecycle speed and efficiency matter.
How it might fit into Incus
A --microvm flag could work similarly to --vm, but spin up a Firecracker or Cloud Hypervisor instance instead of a full QEMU VM.
Existing Incus profiles, networks, and storage backends could still be leveraged where possible.
Users could then choose the right tool for the job:
- LXC containers for traditional system containers
- OCI containers for app-level workloads
- MicroVMs for fast, secure VM isolation
- Full VMs for feature-rich virtualization needs
This is just a suggestion, but I think adding MicroVMs as a first-class option in Incus would make it an even more versatile and modern platform for running mixed workloads.
We’ll soon address all the benefits you’re mentioning, just not with micro VMs (maybe you’ll call that micro VMs, depending on which one of the 200 definitions you choose ).