KRUNVM-CREATE(1)

๐Ÿ“ฆ
version 0.1.6 ยท 2 versions
, in fedora 43

โœจ KRUNVM-CREATE โœจ

okay bestie, so this is the krunvm-create page from the krunvm manual (section 1, the commands section, where all the good stuff lives ๐Ÿ’…) and it's literally just: make a new microVM out of an OCI image. that's the whole vibe. let's get into it ๐Ÿซถ


๐ŸŒธ NAME ๐ŸŒธ

krunvm-create โ€” create a new microVM from an OCI image โœจ

like. it makes a microVM. from an image. no cap.


๐ŸŽ€ SYNOPSIS ๐ŸŽ€

krunvm create [OPTIONS] IMAGE

that's it, that's the summoning ritual ๐Ÿ”ฎ


๐Ÿ’– DESCRIPTION ๐Ÿ’–

so krunvm create creates a new microVM from the OCI image you hand it in the IMAGE argument. ๐Ÿฆ‹

and if you're like "bestie what even counts as an IMAGE around here" โ€” please go read buildah-from(1), it explains the format that IMAGE supports. i'm not gatekeeping, i'm just saying the format lore lives over there ๐Ÿ“–โœจ


๐Ÿ‘‘ OPTIONS ๐Ÿ‘‘

  • --cpus NUM โ€” the number of vCPUs that get created for this microVM. more cpus = more main character energy, but also like, be reasonable ๐Ÿซถ
  • --mem NUM โ€” the amount of RAM, in MiB, that will be available to this microVM. ๐Ÿง 

and here's the cute part: the memory you configure for the microVM is not reserved immediately. instead it gets provided as the guest demands it, and both the guest and libkrun (which is acting as the Virtual Machine Monitor) will attempt to return as many pages as possible back to the host. so it's giving generous-but-tidy, not hoarder โœจ

  • --name NAME โ€” the name to be assigned to this microVM. give it a name, it deserves one ๐Ÿฅบ
  • -p, --port HOST_PORT:GUEST_PORT โ€” exposes a port in the guest running in the microVM through a port in the host. ๐ŸŒˆ

you can specify this option multiple times to expose as many guest ports as you want. go off, expose them all ๐Ÿ’…

  • -v, --volume HOST_PATH:GUEST_PATH โ€” makes HOST_PATH visible in the guest running in the microVM through GUEST_PATH. ๐Ÿ“

this option can also be specified multiple times to make more paths in the host visible in the guest. stack 'em up ๐Ÿงš

  • -w, --workdir GUEST_PATH โ€” configures GUEST_PATH as the working directory for the first binary executed in the microVM. like, where the whole thing kicks off ๐ŸŽฌ

๐Ÿ”ฅ SEE ALSO ๐Ÿ”ฅ

buildah(1), buildah-from(1), krunvm(1), krunvm-changevm(1)

(go read these, they're the extended universe iykyk ๐Ÿ“š)


ok real talk bestie, quick vibe check on the whole thing: krunvm create [OPTIONS] IMAGE is the move, every flag above is exact, and the memory thing is lazy on purpose โ€” that's a feature, not a bug, don't panic ๐Ÿ’–

and that's the page!! this version is from the krunvm manual, dated 2025-07-25, and the header/footer both say KRUNVM-CREATE(1) because that's literally the name of the page bestie ๐Ÿ˜ญ๐Ÿ’œ slay, go build a tiny VM, mwah ๐ŸŽ€โœจ

๐Ÿ“ฆ where this page comes from
  • fedora 43: krunvm 0.1.6-11.fc43 ยท Apache-2.0 AND MIT AND (MIT OR Apache-2.0) AND (MIT OR X11 OR Apache-2.0)
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms