summaryrefslogtreecommitdiffstats
path: root/STATE-CURRENT.md
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-16 22:55:55 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-16 22:55:55 -0500
commit6107a002a5fb532f0b673c107c4cbe5d0d8925b4 (patch)
tree36301e7d785c6855969d0145d6286552f443cc82 /STATE-CURRENT.md
parenta06d4b13cf209c2ce74a79a5565787e2edcbf0d8 (diff)
downloadopen-iov-6107a002a5fb532f0b673c107c4cbe5d0d8925b4.tar.gz
open-iov-6107a002a5fb532f0b673c107c4cbe5d0d8925b4.zip
docs(wiki): 2026-11-16 evening status refresh - host draw chain proven end to end, guest submission is the wall
- 11 wiki pages refreshed: the real frame pushes are admitted (persisted colour-target bind, draw markers inside counted runs, 40-chunk full-window replay, 128-slot ring); the beef draw lane latches a clean DS at the live-derived GS map; capture-less boots get the golden 2799-word MME pack; CALL hold/carry fire/SA re-arm fire with the latch kept across the channel recycle. - Decisive finding recorded as guest-side: 36 boots (c990-c1019) show no non-null CALL(34) draw macro from the client (interior 0x3910/0x3914 writes carry data=0x0) plus guest EGL/dri2 failures and OOM kills. - GZDoom video delivered via the guest software GL path (Mesa llvmpipe) is documented as a non-vGPU deliverable. - STATE-CURRENT.md snapshot prepended; wiki published to open-iov.org (revs 24210-24220; 68 pages audited, 0 problems).
Diffstat (limited to 'STATE-CURRENT.md')
-rw-r--r--STATE-CURRENT.md61
1 files changed, 61 insertions, 0 deletions
diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index f1d8313..f18d3be 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,5 +1,66 @@
# Open-IOV Current State
+> **Snapshot: 2026-11-16 ~22:55 (SESSION 157 continued; HEAD `a06d4b13` ==
+> `vgpu/master`; the working tree carries only this docs refresh; supersedes
+> the 2026-11-16 ~00:35 entry below).**
+> The graphics front crossed from "the `DRAW_IAB` macro executes end to end"
+> to "the **host-side draw chain is proven end to end; the decisive wall is
+> guest-side submission**".
+>
+> - **The host chain is deterministic.** The real frame pushes are admitted
+> (a persisted colour-target bind carried from an earlier trusted push,
+> draw markers accepted inside counted method runs, the 14.8-thousand-word
+> window replayed as 40 chunks, a data-led window-start snap, a 128-slot
+> candidate ring); the beef draw lane latches a **clean DS**
+> (`DS-FAST2 ... ds_after=80000000`, c963) at the live-derived GS attribute
+> map (maps=6, no SPH18), with the draw anchor moved after the first
+> `0x3810` vertex-stream run and the raster enables emitted. Capture-less
+> boots get a **golden 2799-word MME pack** from the golden library
+> (`MME-GOLDEN`/`MME-PRELUDE`), and `MME-CALL-HOLD -> MME-CARRY-SAVE ->
+> MME-CARRY-FIRE -> MME-PACK-REARM -> MME-SA-REARM` fires; the prelude
+> latch survives the per-fire channel recycle (`MME-LATCH-KEEP`) and every
+> admitted-window chunk is forwarded in order.
+> - **The decisive finding is guest-side** (c990-c1019, 36 boots): the client
+> never submits a non-null `CALL(34)` draw macro — every `0x3910/0x3914`
+> hit is an interior method write with `data=0x0`, no CALL header exists in
+> the admitted windows (`DRAW-SCAN-PRE` found=0), and those cycles logged
+> guest EGL/dri2 failures and OOM kills (six missions `frames=0`). The vGPU
+> path still stores nothing (`wrote=0`, `0/1025`, `px0=0`); the next work
+> is guest-first — repair/verify the guest GL/EGL path and memory, then
+> capture one real frame submission.
+> - **GZDoom video delivered** through the guest's **software GL** path (Mesa
+> llvmpipe), not the emulated GPU: four byte-verified files (22 s flight +
+> 18 s orbit, 640x480/1280x960, 30 fps) at
+> `https://files.vgpu.io/files/open-iov-gzdoom-20261116`. It is a
+> guaranteed-quality deliverable, not a vGPU rendering claim.
+> - **Host incident and recovery:** `vgsp` stuck in the UNLOADING state at
+> 09:12 (a sema-service work item never completed; `refcnt=-1`, both
+> `rmmod` and `insmod` blocked). An approved reboot was executed and the
+> host recovered; follow-up: make the sema-service work quiesce bounded so
+> a stuck item can never wedge unload again.
+> - Commits since the last snapshot: eng89..eng89r (`ed8a9c6b`, `630f5a0d`,
+> `d2f08383`, `42a9a97b`, `cb008b85`, `4e888f4d`, `9c09d3bf`, `60b1bf75`,
+> `9731649e`, `d9645c7d`, `47a82e6a`, `ffa7e596`, `1ae572c9`, `ebacf220`,
+> `a644d254`, `f0e34c4f`, `116b0ba7`, `a06d4b13`), plus the guest tooling
+> `9c36fba4`; HEAD `a06d4b13` == `vgpu/master`, working tree clean before
+> this refresh.
+>
+> CUDA front unchanged (backgrounded while graphics holds the device; its
+> 10-30 status stands): `41343c63` green (`victory_mail` `VADD bad=0` +
+> `STATUS OK`; `vecadd_loop` 100 launches PASS); the fresh-boot battery's red
+> class is D2H-stage with release-discipline fixes staged; the SESSION 143
+> Vulkan fence regression is not re-measured.
+>
+> Live at check (read-only): host uptime 13 h 38 m (boot 2026-11-16 ~09:13,
+> the approved recovery reboot); `vgsp` loaded (refcount 0); the campaign
+> rotated its mdev from `6034deec-1bab-4ecc-b383-5608be912e18` to
+> `5aafbae7-de3d-44e0-acaa-8b1d97cbdbfb` at 22:52 with a fresh QEMU cycle
+> (12 GiB file-backed guest, kvmfr ivshmem); X alive (display-channel polls
+> advancing); `nvidia-smi` reports no GPU (the claim is held); pstore empty;
+> no Xid/Oops; no reboot initiated during the check. The open-iov.org wiki
+> was refreshed alongside this snapshot (11 pages, revs 24210-24220; 68
+> pages audited, 0 problems).
+>
> **Snapshot: 2026-11-16 ~00:35 (SESSION 157 continued; HEAD `88d5005a` ==
> `vgpu/master`; working tree clean; supersedes the 2026-11-15 ~16:35 entry
> below).**