Repository navigation
SYS REQ 034
The native live-assistance system shall refuse VM dispatch unless its approved storage reserve and unique loopback host-to-guest port plan are available.
An import that consumes most of the remaining NVMe space or collides with an existing VM's forwarded ports can strand an authorized one-shot run. Recovery must not silently delete operator data or widen network exposure.
The host computes required free bytes from the pinned image/import profile, planned local artifacts, and an operator-approved retained reserve before claiming the one-use permit. It binds a collision-free, loopback-only host-port set to the run profile before dispatch and verifies the exact VM forwarding table afterward. Insufficient capacity or a port conflict returns a redacted finding and consumes neither the provisioning dispatch nor existing user data.
TEST-133 injects insufficient capacity and proves refusal before permit claim/dispatch or deletion. TEST-134 injects occupied and duplicate ports and proves no VM dispatch or non-loopback forward. System-level native Windows verification remains planned.
System-Requirements-Specification; epic #250; P2 #255
High
Planned storage- and port-preflight records bound to the policy/profile digest, with unchanged VM inventory, unclaimed dispatch ledger, preserved operator data, and exact loopback mapping.
Planned host-run preflight allocating to REQ-131, REQ-132, and REQ-133 around the one-shot provisioner and VirtualBox adapter in scripts/assisted_benchmark_virtualbox.py; current adapter tests do not yet exercise host-profile capacity reporting or run-specific port allocation.
Planned; insufficient-space and port-collision behavior are not yet integrated with the run planner.