Holos
QEMU/KVM with a compose-style YAML, GPUs and health checks
Details
- External ID
- 47840851
- Source
- HN
- Company
- —
- Product
- Holos
- Website domain
- github.com
- Launched
- April 20, 2026
- Cohort
- —
- Upvotes
- 56
- Upvotes percentile
- 0.8451156812339332
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
I got tired of libvirt XML and Vagrant's Ruby/reload dance for single-host VM stacks, so I built a compose-style runtime directly on QEMU/KVM.What's there: GPU passthrough as a first-class primitive (VFIO, OVMF, per-instance EFI vars), healthchecks that gate depends_on over SSH, socket-multicast L2 between VMs with no root and no bridge config, cloud-init wired through the YAML, Dockerfile support for provisioning.What it's not: Kubernetes. No clustering, no live migration, no control plane. Single host. Prototype, but I'm running it on real hardware. Curious what breaks for people.
Enrichment
- Theme
- lightweight and on-device AI runtimes
- Vertical
- Horizontal
- Function
- Model & infra
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- qemu virtualization with yaml configuration
- Manually corrected
- False
Could you build this?
No Building a custom virtualization orchestrator directly on QEMU/KVM with VFIO GPU passthrough, EFI var manipulation, and L2 multicast networking demands low-level Linux systems programming.
What it would actually take: This project requires writing a systems daemon (typically in Rust, C, or Go) interacting directly with Linux kernel subsystems like VFIO, IOMMU, kvm.ko, tap devices, and OVMF firmware binaries. The hard parts are orchestrating PCI device unbinding/rebinding, managing hardware IOMMU groups safely, configuring per-instance NVRAM states, and managing non-blocking socket-multicast virtual network interfaces. It requires deep expertise in Linux kernel internals, hardware virtualization, and low-level systems programming.
Discussion
20 comments analyzed.
Competitors mentioned: Incus (lightweight QEMU interface), Vagrant (VM provisioning tool), Pulumi with Incus provider, Pyinfra (provisioning), Docker/Docker Compose
Concerns raised: QEMU command-line options change arbitrarily across versions, Managing state in multiple places (Pulumi, Incus, host), Windows/macOS provisioning not yet implemented, No daemon means no easy VM import capability, YAML-based configs encourage DSL hacks instead of proper programming
Feature requests: holos run CLI command (docker run equivalent, not just compose), Windows unattended install support (autounattend.xml), macOS provisioning support, Import existing VMs functionality, Better QEMU version compatibility documentation
Competitors
Other products that read as similar to this one — 92 launches clear the similarity bar, closest 8 shown.
Attention rank: #21 of 93 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 173 days after the earliest competitor.
- CUDA/graphics in QEMU-KVM VMs without passing the Nvidia card to them · hn · 2026-09-08 · 5 upvotes · similarity 0.52
- VMetal · hn · 2026-03-19 · 12 upvotes · similarity 0.48
- VM-curator · hn · 2026-01-25 · 42 upvotes · similarity 0.48
- LLMKube · hn · 2025-11-18 · 5 upvotes · similarity 0.45
- Docker Model Runner Integrates vLLM for High-Throughput Inference · hn · 2025-11-20 · 7 upvotes · similarity 0.44
- Kappal · hn · 2026-02-05 · 50 upvotes · similarity 0.43
- kairon · github · 2026-09-11 · 11 upvotes · similarity 0.43
- podup · ph · 2026-09-07 · 1 upvotes · similarity 0.41
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a model & infra tool for Fintech yet.