Repository navigation
REQ 056
Windows provisioning shall revalidate the current guest boot after a managed or detected reboot before continuing.
A prior boot's ready status cannot prove that WinRM and its firewall survived a reboot.
A managed power cycle requires observed poweroff followed by running, a new boot ID, fresh witness status, and encrypted authenticated readback. A guest-only reboot additionally requires independently corroborated boot evidence; the source, failure modes, comparison, and receipt encoding must be proven and specified before it can pass. Until then its result is unknown. Pending obligations and their baselines survive crashes and cannot be cleared by omitting a baseline or issuing an unrelated recheck; lost or rolled-back continuity is unknown. An initially powered-off VM with independently established baseline-free genesis may prove a separately labeled fresh start, but not a full Windows kernel restart or prior-to-current reboot comparison.
Planned, TEST-056; neither old VBox markers nor a completion file satisfies this test.
Software-Requirements-Specification
High
Planned counter, guest-reboot, anti-rollback, crash-recovery, and power-cycle evidence tests
Windows workflow, planned boot witness
Planned