SPspwa4·Apr 21, 2026
See https://github.com/zeroecco/holos/blob/5f5e60f753c5e99c421db...
Qemu command-line calls
In Show HN: Holos – QEMU/KVM with a compose-style YAML, GPUs and health checkszeroecco
holos
Go2026–2026
zeroecco / holos
holos
docker compose for kvm/qemu
2Distinct people
2Mentions
0Explicit recommenders
147GitHub stars
What to know before exploring
What it is
docker compose for kvm/qemu
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by hour2 dated mentions
Observed mentions: 2026-04-20 21:13:49 UTC to 2026-04-21 12:01:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 20, 21:00 | 2026-04-20 21:00:00 UTC | 2026-04-20 22:00:00 UTC | 1 | 1 | 0 |
| Apr 20, 22:00 | 2026-04-20 22:00:00 UTC | 2026-04-20 23:00:00 UTC | 0 | 0 | 0 |
| Apr 20, 23:00 | 2026-04-20 23:00:00 UTC | 2026-04-21 00:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 00:00 | 2026-04-21 00:00:00 UTC | 2026-04-21 01:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 01:00 | 2026-04-21 01:00:00 UTC | 2026-04-21 02:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 02:00 | 2026-04-21 02:00:00 UTC | 2026-04-21 03:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 03:00 | 2026-04-21 03:00:00 UTC | 2026-04-21 04:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 04:00 | 2026-04-21 04:00:00 UTC | 2026-04-21 05:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 05:00 | 2026-04-21 05:00:00 UTC | 2026-04-21 06:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 06:00 | 2026-04-21 06:00:00 UTC | 2026-04-21 07:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 07:00 | 2026-04-21 07:00:00 UTC | 2026-04-21 08:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 08:00 | 2026-04-21 08:00:00 UTC | 2026-04-21 09:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 09:00 | 2026-04-21 09:00:00 UTC | 2026-04-21 10:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 10:00 | 2026-04-21 10:00:00 UTC | 2026-04-21 11:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 11:00 | 2026-04-21 11:00:00 UTC | 2026-04-21 12:00:00 UTC | 0 | 0 | 0 |
| Apr 21, 12:00 | 2026-04-21 12:00:00 UTC | 2026-04-21 13:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesShow HN: Holos – QEMU/KVM with a compose-style YAML, GPUs and health checks
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.
56 points · Open discussion