authoravatarclover caruso<git@paperclover.net>2026-10-20 15:01:32-07:00
committeravatarclover caruso<git@paperclover.net>2026-10-21 02:52:29-07:00
logb58af12506db1360952b0e6832425927c5cd8ab9
tree48228c59df1c6b0622417c7128cb8ed028ca37fc
parent62f43140a5416bc7200a2df5f7b4a33f26400c29
signature Signed by SSH key SHA256:52mNGHRsVFBDED9IAX5pe+LRWUefqTbxEReunq21QvU

Record setup VM retirement and fresh Windows boot timing

Assisted-by: gpt-6-astra

2 files changed, 61 insertions(+), 0 deletions(-)

tools/vm-retirement.md created+27
...@@ -0,0 +1,27 @@
1# Setup VM retirement
2
3On 2026-10-20, Clover requested removing every leftover NAS VM while preserving
4her personal Mac development VM and the prepared OS library. The seven retired
5guests were `win-modern-w11-clone-fallback`, `ubuntu-arm-proof`,
6`testbox-windows-8-pro-4c7886b3`, `testbox-windows-10-pro-4752fd14`, `openclaw`,
7`init-win10-ssd-proof-11`, and `window-stream-win11-test`.
8
9The published Windows 11, Ubuntu ARM64, Windows 8, and Windows 10 templates
10passed image checks before instance deletion. The OS library remains intact.
11Graceful shutdown was attempted first; the unresponsive, disposable SSD
12benchmark guest required force-off. Instance disks, firmware, TPM state, and
13managed-save state were removed. Unreferenced benchmark images on SSD were
14also removed. The Mac VM was neither stopped nor restarted.
15
16OpenClaw's service declaration is disabled, preventing deployment from
17recreating its VM. Its stopped dataset remains at `/srv/prod/openclaw`, including
18the disk, private configuration, keys, and original domain definition. Snapshot
19`globe/prod/openclaw@retired-20261020T2200` has hold `openclaw-retirement`.
20This private state is not published as a general OS preset. Later routine
21deployment backups omit the retired service; preserve the dataset and hold.
22
23The old VM definitions and the Windows timing trace are retained owner-only
24under `/var/lib/snowglobe/retirements/vms-20261020`. The obsolete OpenClaw
25libvirt dependency and resource-slice overrides were removed. Restoring
26OpenClaw requires a deliberate production deployment of its enabled service;
27its preparation script can recreate the definition from the retained disk.
tools/windows-presets.md+34
...@@ -48,3 +48,37 @@ The published v10 preset supersedes v4. v4 and earlier referenced bases remain...@@ -48,3 +48,37 @@ The published v10 preset supersedes v4. v4 and earlier referenced bases remain
48available to their existing guests. Reverting the default requires withdrawing48available to their existing guests. Reverting the default requires withdrawing
49v10 from discovery while preserving its bytes wherever clones still reference49v10 from discovery while preserving its bytes wherever clones still reference
50them; it does not require modifying existing guest disks.50them; it does not require modifying existing guest disks.
51
52## First-run timing after fleet retirement
53
54After [retiring the unused guests](vm-retirement.md), another disposable v10
55clone reached `ready` in 95.75 seconds with the same 4-vCPU/4-GiB configuration.
56The host observed these phases by polling the provisioning markers:
57
58| Phase | Duration |
59| --- | ---: |
60| Create disk clone and start | 1.12 s |
61| First boot through provisioning startup | 48.63 s |
62| Apply account and computer identity | 2.08 s |
63| Restart, log in, and start desktop capture | 43.92 s |
64
65The guest agent first answered at 33.10 seconds. Guest marker timestamps put
66identity changes at 1.83 seconds; the host's polling rounds this to 2.08 seconds.
67Two Kernel-General boot events confirmed the reboot. Explorer and guest capture
68were running, and the production browser displayed the personalized desktop.
69
70This is a disk template, not a saved-memory resume. `Rename-Computer` in the
71provisioning script is followed by a forced restart; the second boot enables
72capture and waits for the desktop. Avoiding that second boot is the next
73architectural opportunity. Cloning the disk itself is already inexpensive.
74
75By `ready`, QEMU recorded 474 flushes with 46.45 seconds of aggregate duration
76(98 ms per flush), 2.24 GB read, and 105 MB written. These operation durations
77can overlap and are not an additive wall-clock breakdown. The read cache does
78not accelerate synchronous HDD writes. This quieter-host result also has
79different cache warmth, so it does not isolate the benefit of fleet retirement.
80
81The restricted raw trace is
82`/var/lib/snowglobe/retirements/vms-20261020/windows-boot-trace.json`.
83The trace guest was shut down and removed afterward; the published preset and
84personal Mac remained intact.