Windows: would you consider a libkrun/WHP VM backend instead of a WSL 2 distro?

Aperta
#336 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, linux, rust

Direzione di ricerca

Start by reading crates/kiri-vmm and docs/features.md to understand the existing Virtualization.framework backend and the Windows WSL bridge described in the issue. Then check libkrun's current WHP support and whether its kernel, vsock, networking, and memory features meet Kiri's needs. Done would require a reviewed backend proposal covering feasibility, Windows guest assets, and tradeoffs; the issue does not specify implementation steps.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Kiri on Windows today runs the x86-64 Linux build inside a WSL 2 distro, and kiri-win.exe carries the engine API over npipe through one wsl.exe … kiri bridge. That keeps the host side small, but it also means the guest Kiri runs on Windows is Microsoft's kernel, not the 10 MB kernel in guest/kernel that the macOS path is built around. A fair number of the open Windows issues trace back to that one fact:

  • #277 — the WSL kernel boots a hybrid cgroup tree, so kiri-init exits 1
  • #44 — no MASQUERADE rule, so bridge-network containers have no egress
  • #60 — containers reach the internet unfirewalled on kernels before 6.3
  • #209 — BuildKit has no usable DNS
  • #189 — Stop leaves vmmemWSL running with its memory unclaimed
  • #297, #314, #318 — the distro itself as an install and lifecycle dependency
  • and the engine API has to stay on npipe, because WSL's localhost relay drops half-closes (docs/features.md)

So: would you consider giving Windows a VM backend of Kiri's own — libkrun and the Windows Hypervisor Platform — instead of a WSL 2 distro?

What that would bring to the architecture Kiri already has:

  • Your own guest kernel. krun_set_kernel takes a raw Image, so guest/out/Image and its four patches could be the Windows kernel too — cgroup v2, netfilter, the GSO/GRO fixes — instead of whatever WSL ships.
  • A real vsock channel. libkrun provides virtio-vsock, and krun_add_vsock hands the host plain listen/connect fds: the same shape as the kiri-proto link on macOS, and it removes the reason the Windows API sits on npipe at all.
  • virtio-net with host port forwarding, instead of a relay that drops half-closes, plus TSI for containers that only need outbound.
  • virtio-fs and virtio-block — the same devices crates/kiri-vmm already drives on Virtualization.framework, so Windows would be a sibling backend rather than a separate engine.
  • Memory that goes back to Windows. virtio-balloon plus idle vCPUs sleeping in the hypervisor is what #189 asks for. libkrun's own balloon is free-page reporting only, so this one needs checking before it counts.
  • Less install surface. One signed .msi, no distro, no Store, no separate wsl --update to keep working.

What it costs, as far as I can tell: WHP is still a Hyper-V platform feature, so the virtualization prerequisite does not go away (the WSL distro does); libkrun's own README still lists WHP as upcoming; and the WHP path is x86-64 only as far as I can see, so Kiri's Windows on Arm build would be the odd one out or at least unproven. The work is a new backend, not a port.

The only existing evidence I have that libkrun on WHP runs at all is smolvm, which I am mentioning as a data point, not as something for Kiri to depend on. What I would like to know:

  1. Is WSL 2 the intended long-term Windows story, or a stepping stone?
  2. Have you looked at libkrun/WHP and set it aside? If so, on what ground — vsock on Windows, USB passthrough, signing, or the maintainer cost?
  3. Would you review a proposal for a second VM backend? If yes, how would you want the Windows guest assets (kernel, data disk) built and shipped?

Thanks — the macOS and Linux paths are genuinely impressive, and Windows is the one place where it does not feel like the same engine.

Lingua principale
Rust
Stelle
7.5k
Fork
329
Merge medio
7h 48m
PR unite (30g)
105

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di libracoder/kiri

Tutte le issue di libracoder/kiri

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.