Running Windows VMs with the cocoonstack Cloud Hypervisor and firmware forks.
Cocoon supports Windows guests via the --windows flag:
cocoon image pull <cloudimg-url>
cocoon vm run --windows --name win11 --cpu 2 --memory 4G --storage 15G <image-name>
The --windows flag:
kvm_hyperv=on)cocoon-check --upgrade installs the cocoonstack fork dev release build. The virtio-blk DISCARD fix and the virtio-net ctrl_queue tolerance and used_len fix are upstream since v52; the fork adds diff snapshots — see known issuesdev build, what cocoon-check --upgrade installs on x86_64 (EFI ResetSystem for the ACPI power-button and the IA32_FEATURE_CONTROL/VMXON lock — see known issues); upstream 0.5.0 boots Windows but cocoon vm stop falls back to the 30s timeoutPre-built images and build automation are maintained in cocoonstack/windows.
The Windows image is published as an OCI artifact (split qcow2 parts pushed via ORAS), not a runnable OCI container image — use oras pull (not cocoon image pull or docker pull).
# 1. Pull split parts via oras (https://oras.land)
oras pull ghcr.io/cocoonstack/windows/win11:25h2
# 2. Verify the split parts
sha256sum -c SHA256SUMS
# 3. Import the parts into Cocoon in order
cocoon image import win11-25h2 windows-11-25h2.qcow2.*.qcow2.part
cocoon vm console)For more details, see the Cloud Hypervisor Windows documentation.