bounded workload recipe · modeled prerequisites
Proxmox Two-Light-VM Mini PC Workload
A bounded Proxmox VE 9 recipe for two light virtual machines, with explicit CPU, memory, storage, network, and virtualization assumptions.
- record type
- workload
record at a glance
- required checks
- 5
- recommended checks
- 2
- assumptions needing an answer
- 0
- best attached evidence
- grade B
- accepted grade A runs
- 0
decision scope
Prerequisite and planning-budget fit for a single-node host; not VM throughput, resilience, or storage-latency performance.
- application release
- Proxmox VE 9.x
- version scope
- >=9.0.0 <10.0.0
- deployment
- Proxmox VE on bare metal
- nesting depth
- 0
- runtime chain
- Bare-metal x86-64 host
- recipe lifecycle
- candidate
default assumptions
These values are part of the recipe fingerprint. A field labeled “must be answered” is intentionally unknown until the user supplies it.
- guest count
- 2
- allocated guest memory gi b
- 8
- redundant storage available
- no
- decision context
- existing hardware
capability checks
- minimum / recipe-required checks
- 5
- recommended checks
- 2
- 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.
- 64-bit x86 processor
- compute · recipe-required
grade B - one of x86_64 or x86_64-v2
if a profile does not meet it: Proxmox VE requires a compatible Intel 64 or AMD64 processor. - Hardware virtualization
- virtualization · recipe-required
grade B - required
if a profile does not meet it: Hardware virtualization is required for the planned virtual machines. - 12 GiB planning allocation
- memory · recipe-required
grade D - at least 12
if a profile does not meet it: The modeled two-VM allocation needs at least 12 GiB. - SSD-class system storage recommendation
- storage · recommended
grade B - one of nvme-ssd or sata-ssd
if a profile does not meet it: Proxmox recommends fast storage and says SSDs produce the best results. - 128 GiB planning capacity
- storage · recipe-required
grade D - at least 128
if a profile does not meet it: The modeled host and two light guests need at least 128 GiB. - At least one gigabit network interface
- network · recipe-required
grade B - at least 1
if a profile does not meet it: The documented evaluation floor includes a network interface; production guidance is stronger and calls for redundant gigabit-class interfaces. - Redundant or recoverable storage plan
- operational · recommended
grade B - required
if a profile does not meet it: A single mini-PC drive is not a resilient storage design; add redundancy and backups.
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.
- 64-bit x86 processor
- compute · required
- one of x86_64 or x86_64-v2
- Hardware virtualization
- virtualization · required
- required
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 controlled benchmark protocol is maintained for this workload. Its prerequisite rules cannot be presented as measured performance.
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.
receipts
3 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26
record identity, publication and review
- record id
- workload-proxmox-two-light-vms
- canonical path
- /workloads/proxmox-two-light-vms/
- 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.
3 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.
- evidence grade b 2 records
- evidence grade d 1 record
evidence grade b · official sourcesupports
For production, Proxmox VE documents Intel 64 or AMD64 with hardware virtualization, at least 2 GB for host services plus designated guest memory, fast redundant storage with SSDs preferred, and redundant multi-gigabit network interfaces. Its separate evaluation-only minimum is not a production recommendation.
evidence grade b · official sourcesupports
Proxmox VE 9.0 is an official stable release line based on Debian 13, and its ISO is installable directly on bare metal.
evidence grade d · modeled or inferredsupports
Resource allocations in candidate recipes and the starter stack are planning budgets, not measured throughput or latency claims.
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.
- 3 sources
- 2 with a public link
- 1 first party modeling policy
- 1 official application documentation
- 1 official release notes
first party modeling policy · 1 source
- Super Evil Robots Repositioning Master Plan
official application documentation · 1 source
official release notes · 1 source
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.
- — current candidate record reviewed against the attached evidence set.
- — next required review under the weekly software review interval.
- — created: Initial bounded workload recipe created.
inspect the complete generated lifecycle and change-history index