Record the passing KVM integration run; CHANGELOG for validation, UEFI and tracing

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-10 19:13:51 +00:00
parent c4f59bd153
commit cc0606d24f
3 changed files with 56 additions and 2 deletions
@@ -9,7 +9,7 @@ Plan: [2026-09-10-0805-kvm-libvirt-tracing.md](../plans/2026-09-10-0805-kvm-libv
 - [x] Step 4 — Call sites
 - [x] Step 5 — Integration test output
 - [x] Step 6 — Unit tests
- [ ] Step 7 — Docs, execution log, CHANGELOG (docs and this log done; CHANGELOG waits for the live run)
+- [x] Step 7 — Docs, execution log, CHANGELOG

 ## Steps 1–6 — Tracer, pool logging, tests, integration wiring

@@ -98,3 +98,12 @@ trace.go:55: 09:04:33.165 libvirt virDomainCreate domain=proxy-abc123def456ghij
 Worth noting: `length=0` on `virStorageVolUpload` is what the provider
 passes (libvirt reads to EOF); the following `seed volume uploaded`
 line has the byte count.
+
+## Step 7 — Live run confirmed; CHANGELOG
+
+The compact trace was accepted on the first passing live run
+(2026-09-10, beelink): one line per RPC with the libvirt function name,
+the provider's own lines between them, `Provisioning` polls readable at
+a glance (`SrcArp interfaces=0`, `SrcAgent … ErrAgentUnresponsive`
+until the agent came up at +20 s), and a full `ListByTag` sweep over 21
+domains in 15 ms. CHANGELOG entry added under the KVM validation entry.