bounded workload recipe · modeled prerequisites

Home Assistant OS VM Mini PC Workload

A bounded Home Assistant OS generic x86-64 virtual-machine recipe with UEFI, Secure Boot, memory, storage, and virtualization conditions.

record type
workload

record at a glance

required checks
8
recommended checks
0
assumptions needing an answer
1
best attached evidence
grade B
accepted grade A runs
0

decision scope

Prerequisite fit for the specified VM allocation; not an integration-count or recorder-performance benchmark.

application release
Home Assistant Core 2026.7.4
version scope
>=2026.7.4 <2026.8.0
deployment
Home Assistant OS in a KVM virtual machine
nesting depth
1
runtime chain
KVM virtual machine → Home Assistant OS generic x86-64
recipe lifecycle
candidate

inspect the version-scoped application record →

default assumptions

These values are part of the recipe fingerprint. A field labeled “must be answered” is intentionally unknown until the user supplies it.

vm vcpu
2
vm memory gi b
4
vm disk gi b
32
secure boot disabled
must be answered
decision context
existing hardware

capability checks

minimum / recipe-required checks
8
recommended checks
0
workload-dependent boundary
all checks apply only to this bounded recipe

“Required” means required by this maintained recipe; it is not automatically the vendor’s universal minimum. “Recommended” can make a result Conditional but cannot be silently promoted into a hard requirement.

No machine has been selected on this page, so nothing below describes your hardware. Each row states what the recipe expects, then the sentence a profile would receive if it does not meet that expectation.

x86-64 architecture
compute · recipe-required
grade B
one of x86_64 or x86_64-v2
if a profile does not meet it: The selected image requires x86-64.
Hardware virtualization for the VM
virtualization · recipe-required
grade D
required
if a profile does not meet it: The selected deployment is a VM and needs hardware virtualization.
UEFI boot support
operational · recipe-required
grade B
required
if a profile does not meet it: The generic x86-64 Home Assistant OS image expects UEFI.
2 vCPU VM minimum
compute · recipe-required
grade B
at least 2
if a profile does not meet it: Home Assistant OS documents a minimum allocation of 2 vCPUs for a virtual machine.
2 GiB VM memory minimum
memory · recipe-required
grade B
at least 2
if a profile does not meet it: Home Assistant OS documents a minimum allocation of 2 GiB RAM for a virtual machine.
4 GiB VM planning budget
memory · recipe-required
grade D
at least 4
if a profile does not meet it: This modeled Home Assistant VM allocates 4 GiB.
32 GiB VM disk planning budget
storage · recipe-required
grade D
at least 32
if a profile does not meet it: This modeled VM allocates a 32 GiB disk.
Secure Boot disabled
operational · recipe-required
grade B
required
if a profile does not meet it: Confirm that Secure Boot is disabled before treating the setup as compatible.

architecture and acceleration conditions

Each row here already appears in the capability check list above. This section repeats the checks that turn on instruction set, media engine, or virtualization support. The full check list carries the sentence each row produces when a profile does not meet it.

x86-64 architecture
compute · required
one of x86_64 or x86_64-v2
Hardware virtualization for the VM
virtualization · required
required
2 vCPU VM minimum
compute · required
at least 2

known issues in this app and workload scope

No known issue is attached to this app/version/workload scope. That means “none recorded” as of the review date, not proof that no issue exists.

benchmark protocol and tested hardware

No exact hardware configuration has an accepted Grade A run for this workload. The result ledger is empty and no measured throughput, stability, thermal, or power claim is made.

performance boundary

This recipe has 0 accepted Grade A runs. It can evaluate maintained prerequisites and explicit planning assumptions. It cannot claim measured throughput, latency, stability, thermals, power, or workload quality.

evaluate this recipe on an exact profile

receipts

4 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26

record identity, publication and review

record id
workload-home-assistant-os-vm
canonical path
/workloads/home-assistant-os-vm/
publication
candidate · 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.

  1. evidence grade b · official sourcesupports

    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.

    source: Home Assistant OS generic x86-64 board supportchecked 2026-07-26claim: claim-haos-generic-x86-requirements

  2. evidence grade b · official sourcesupports

    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.

    source: Home Assistant OS virtual-machine installationchecked 2026-07-26claim: claim-haos-vm-requirements

  3. evidence grade b · official sourcesupports

    The official July 2026 release notes list Home Assistant Core patch release 2026.7.4.

    source: Home Assistant 2026.7 release noteschecked 2026-07-26claim: claim-haos-release-2026-7-4

1 further grade d record · modeled or inferred
  1. evidence grade d · modeled or inferredsupports

    Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.

    source: Super Evil Robots Repositioning Master Planchecked 2026-07-26claim: claim-ser-workload-budget-model

    limitation: This is a modeled or inferred claim. It cannot establish measured performance.

source ledger

Official facts and first-party modeling are shown separately. Source prose, tables, and diagrams are not republished.

  • 4 sources
  • 3 with a public link
  • 1 first party modeling policy
  • 2 official application documentation
  • 1 official release notes
first party modeling policy · 1 source
  1. Super Evil Robots Repositioning Master PlanSuper Evil Robots · first party modeling policy · checked 2026-07-26 · docs/super-evil-robots-repositioning-plan.md
official application documentation · 2 sources
  1. Home Assistant OS generic x86-64 board supportOpen Home Foundation · official application documentation · checked 2026-07-26
  2. Home Assistant OS virtual-machine installationOpen Home Foundation · official application documentation · checked 2026-07-26
official release notes · 1 source
  1. Home Assistant 2026.7 release notesOpen Home Foundation · official release notes · checked 2026-07-26

record and source history

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.

  1. — current candidate record reviewed against the attached evidence set.
  2. — next required review under the weekly software review interval.
  3. — created: Initial bounded workload recipe created.

inspect the complete generated lifecycle and change-history index