Resources
FAQ
Common questions about mvm, SDKs, Nix, OCI, and platform support.
Is mvm local or hosted?
Section titled “Is mvm local or hosted?”mvm is the local runtime substrate. These docs focus on local build, launch, SDK, and microVM lifecycle behavior.
Is OCI the core runtime model?
Section titled “Is OCI the core runtime model?”No. OCI is a compatibility input. The core model is Nix-built microVM artifacts, signed plans, explicit policy, and audit records.
Why is there a builder VM?
Section titled “Why is there a builder VM?”The builder VM provides a Linux execution boundary for Nix builds and microVM image assembly. It also keeps Linux-only tooling out of host-side cargo workflows.
Does Windows support ship today?
Section titled “Does Windows support ship today?”No. Native Windows is future work tracked by
mvm#428, and WSL2 is not a
supported workload path either — mvm detects WSL2 as its own platform and
refuses the libkrun backend there unconditionally, whether or not the distro
exposes nested /dev/kvm. mvmctl doctor says so directly. Use native Linux
with /dev/kvm or an Apple Silicon Mac.
Which SDK should I use?
Section titled “Which SDK should I use?”Use Python or TypeScript for the current high-level runtime/declaration surfaces. Use Rust for typed Workload IR generation and lower-level tooling.
When should I use static decorators?
Section titled “When should I use static decorators?”Use static decorators for deployable workloads when you want declarations compiled without importing user modules.
When should I use runtime SDK scripts?
Section titled “When should I use runtime SDK scripts?”Use runtime SDK scripts when your application owns sandbox lifecycle. Remember that record/live mode executes host-side SDK code.