From 138fe8d19f779191b23115e2e352ff288402ece1 Mon Sep 17 00:00:00 2001 From: Simone Date: Mon, 25 May 2026 22:27:00 +0200 Subject: [PATCH] docs(runbook): fix B8 template name (WinBuild2025, not 2022) Co-Authored-By: Claude Sonnet 4.6 --- docs/RUNBOOK.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/RUNBOOK.md b/docs/RUNBOOK.md index 5cf8a0c..92f7e9d 100644 --- a/docs/RUNBOOK.md +++ b/docs/RUNBOOK.md @@ -417,10 +417,10 @@ additional runs may close the gap. No non-IP phase regressed. --- -## 8. Static IP baseline — WinBuild2022 with ip_pool (B8 result) +## 8. Static IP baseline — WinBuild2025 with ip_pool (B8 result) Recorded 2026-05-25 — `Measure-CIBenchmark.ps1 -StaticIP 192.168.79.200 -Iterations 4`, -Linux Mint host, template `WinBuild2022` / snapshot `BaseClean`. +Linux Mint host, template `WinBuild2025` / snapshot `BaseClean`. `guestinfo.ip-assignment` injected into cloned VMX before start; `ci-static-ip.ps1` scheduled task applies IP at boot and writes back `guestinfo.ci-ip`. IP column = time until `guestinfo.ci-ip` readable via @@ -452,6 +452,6 @@ Ready column = WinRM/5986 TCP probe after IP known. `guestinfo.ci-ip` is written — no additional TCP probe wait. - `ci-static-ip.ps1` startup latency (~21.8 s) is the new floor; it reflects Windows boot + Task Scheduler + NIC reconfiguration time. -- Destroy is slower on WinBuild2022 (~10 s vs ~5 s on WinBuild2025) — - unrelated to static IP; likely VMDK or snapshot difference. +- Destroy is slower than B7 (~10 s vs ~5 s) despite same template — + likely due to different clone state or disk pressure at test time.