Compute dashboard: 'my_hypervisor: binary not found' + critical banner on dev machines #110

New issue

Closed

opened 2026-05-13 06:51:24 +00:00 by zaelgohary · 1 comment

zaelgohary commented

2026-05-13 06:51:24 +00:00

Member

The Hero Compute island shows a red 'Critical service(s) unavailable.' banner because my_hypervisor is missing on dev hosts.

Status table:

Compute Server: connected
my_hypervisor: binary not found (red)
hero_proc: socket found
cloud-hypervisor: managed by my_hypervisor
mycelium: networking layer
Central Config / Image Registry: configured

Expected on a dev machine

my_hypervisor is a production-host runtime dep (KVM-backed VM lifecycle). It's not realistic to install on a dev laptop. The dashboard should either:

treat it as non-critical when a HERO_DEV_MODE env is set, or
downgrade the banner severity, or
show a dev-mode hint ("not installed on this host - run in production for full functionality")

Repro

Hero OS dock -> Admin -> Compute.

Critical banner fires for any host without my_hypervisor on PATH.

The Hero Compute island shows a red 'Critical service(s) unavailable.' banner because `my_hypervisor` is missing on dev hosts. Status table: - Compute Server: connected - my_hypervisor: **binary not found** (red) - hero_proc: socket found - cloud-hypervisor: managed by my_hypervisor - mycelium: networking layer - Central Config / Image Registry: configured ## Expected on a dev machine `my_hypervisor` is a production-host runtime dep (KVM-backed VM lifecycle). It's not realistic to install on a dev laptop. The dashboard should either: - treat it as non-critical when a `HERO_DEV_MODE` env is set, or - downgrade the banner severity, or - show a dev-mode hint ("not installed on this host - run in production for full functionality") ## Repro Hero OS dock -> Admin -> Compute. Critical banner fires for any host without `my_hypervisor` on PATH.