Version-scoped Home Assistant OS generic x86-64 requirements and VM conditions used by the pilot evaluator.
record type
app
record at a glance
release scope
>=2026.7.4 <2026.8.0
public recipes
1
best attached evidence
grade B
accepted grade A runs
0
version contract
application
Home Assistant Core
modeled release
2026.7.4
effective version range
>=2026.7.4 <2026.8.0
record state
candidate
Home Assistant OS generic x86-64 runtime
18.1 (>=18.1 <19.0)
A future release outside >=2026.7.4 <2026.8.0 requires impact review. This page must not silently transfer these requirements to a materially different version. The appliance runtime has its own independently sourced version contract above; either contract changing requires review.
deployment methods in scope
nesting depth 1
Home Assistant OS in a KVM virtual machine
runtime: KVM virtual machine → Home Assistant OS generic x86-64 18.1 (>=18.1 <19.0) · nesting depth 1
This deployment method is modeled by the pilot but has not been reproduced in an accepted physical-mini-PC lab run.
requirements used by public recipes
Home Assistant OS virtual machine
Prerequisite fit for the specified VM allocation; not an integration-count or recorder-performance benchmark.
No known issue is attached to this exact version scope in the current graph. That means “none recorded,” not proof that no issue exists; the weekly review deadline remains visible above.
No exact hardware configuration has an accepted Grade A result for this application version. The page therefore makes no measured performance claim.
what these requirements do not prove
They do not prove sustained throughput, latency, stability, thermals, or power.
They do not prove that every codec, integration, plugin, or storage topology works.
They do not turn a platform family into an exact physical configuration.
They do not authorize a “recommended” ranking without a declared workload.
Scoped Grade A results: 0. This page exposes version-scoped prerequisites from official sources and the pilot’s modeling boundary.
receipts
4 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26
record identity, publication and review
record id
app-home-assistant-2026-7
canonical path
/apps/home-assistant/
publication
preview · noindex
reviewed
2026-07-26
review again by
2026-08-02
evidence boundary
Grade A count: 0. A Grade B source can establish a documented specification or requirement. Grade D records are modeling inputs. Neither is proof of measured throughput, thermals, power, reliability, or physical fit.
4 attached evidence records
a grade describes how well attested a statement is, not how good the hardware is. grade a is a lab run we reproduced with a published method. grade d is a model, a reasoned inference, or a single unverified report.
The generic x86-64 Home Assistant OS image requires x86-64, UEFI boot, compatible storage, and a supported network adapter; Secure Boot must be disabled.
Home Assistant documents a KVM/Proxmox QCOW2 deployment with minimum VM resources of 2 GB RAM and 2 vCPUs, requires UEFI, and directs KVM users to a non-Secure-Boot OVMF image. The example KVM command allocates 4 GB, while the guide says resources should be sized to the expected workload rather than asserting a universal higher recommendation.
This projection is generated from homelab graph version 0.1.0. The generated lifecycle index exposes only history events that are explicitly present in the structured record. It does not invent an earlier revision when the graph contains only its creation baseline.
— current preview record reviewed against the attached evidence set.
— next required review under the weekly software review interval.
— created: Initial version-scoped software record created.
