OpenVMX V0.7-11

OVMX V0.7-11 Release Notes

Generated by tools/gen_release_notes.py from the merged history since V0.7-10 (22 commits). Do not hand-edit this file -- re-run the tool against the release tag instead.

Highlights

• aarch64 downloads, for the first time. Every earlier release shipped x86_64, Alpha and VAX assets only. V0.7-11 adds a bootable aarch64 set: an arm64 kernel Image (vmlinuz) with the signed in-tree vms.ko, the slim initramfs, the pre-installed ovmx-distrib.img and the OS kit, attached to the release with an -AARCH64 suffix (for example vmlinuz-AARCH64). It is built on an arm64 runner from the tagged commit by the same Dockerfile.bootable pipeline as x86_64. The release-acceptance gate boots those exact files under qemu-system-aarch64 -machine virt, runs PARTS and checks the shipped version. If the aarch64 build fails, the whole cut fails (vms-32aa, vms-b58, vms-a07).
• Clusterwide logical names: a database OVMX cannot decode no longer hangs a member. When OVMX pulls a member's clusterwide logical-name database and cannot decode all of it, OVMX still answers, so the member's startup goes on. OVMX then marks its own clusterwide tables as not synchronized. It refuses to translate or change names in those tables until a later pull succeeds, so it never answers from a partial copy (vms-94a).
• DEFINE, ASSIGN and DEASSIGN take /TABLE=name and reach the executive's own tables, including LNM$SYSCLUSTER. A table this node does not hold is refused with %SYSTEM-F-NOLOGTAB, and nothing is written (vms-aae).

Known open items

• The LOCKMGRERR bugcheck (vms-c55) is not fixed. In the cluster demo, a real VAX running OpenVMS V7.3 still bugchecks with LOCKMGRERR now and then. V0.7-11 includes a change that stops OVMX from removing a directory entry and then asking about that same entry (#1715), but the bugcheck still happens with it. Because the crash is intermittent, a gate run with 0 bugchecks does not show that it is gone.
• The cluster demo does not pass its visitor gate yet. The pre-tag gate (openvmx-site run 38824925565) ran 8 visitor orders, with both OVMX nodes built from this release. All 8 reached CN=3 and the real VAX admitted both OVMX nodes, with 0 VAX bugchecks. In all 8, the OVMX/VAX node stopped during startup after the state transition and never offered Username: (vms-97c2).
• The 0b/05 database request names transfer connection 0, where real requests name one (19 of 19 in the capture corpus) (vms-9045).
• Clusterwide logical names are not sent from OVMX yet. A local change to a clusterwide table is refused with SS$_UNSUPPORTED while other members exist (vms-94a follow-up).
• Lock-tree remastering on the wire is not done yet (vms-380), and a former master does not yet answer "not master here" (vms-657).

Features

• cut: V0.7-11 -- aarch64 downloads ship for the first time (vms-32aa, vms-b58) (#1733)
• vms-6e6: body[28:30] of a lock request is a FIELD, and the corpus already proved it (#1731)
• a cross-node lock request names the requesting process (faithfulness; does not fix vms-c55) (#1730)
• vms-97c2: a cross-node lock request whose frame could not go out is retried, never dropped on a sleeping $ENQW (#1729)
• vms-32aa+b58: aarch64 ships -- the cut builds, attaches and boots a bootable aarch64 set (#1727)
• vms-e79: the cluster demo's emulator builds on WASMFS; the sentinel probes the live fs backend (qemu-wasm-fs, expect wasmfs) (#1728)
• vms-a07: the OVMX kernel and signed vms.ko cross-build for arm64 and boot under qemu-system-aarch64 with /dev/vms (#1726)
• vms-e79: when Node A's worker heartbeat freezes, the visitor gate keeps the worker's JS stack (#1725)
• vms-e79: the drift sentinel checks the in-browser emulator's pthread pool (expect: 16) (#1724)
• vms-208f: the single-node OVMX/VAX browser demo disk follows the tag (built + proven with Node B, attached with a sidecar) (#1723)
• cluster-demo-nodeB: a dispatch whose ref is a release tag attaches Node B to that release (catch-up for V0.7-10, vms-fbdd) (#1719)
• vms-c55: this node never tells a directory to forget a resource and then asks it who masters that same resource (#1715)
• vms-ac4f: ground the directory answer and the rebuild echo -- the conformance ratchet moves from 1 covered frame to 526 (#1717)
• vms-c55: the LOCKMGRERR captured frame-for-frame — OVMX asks where a real VAX tells, and asks about the entry it just removed (#1714)
• vms-649a: the VAX login probe reads the DCL prompt VMS writes; sysboot-single runs in CI (#1712)
• vms-fd8: one deploy inventory and a drift sentinel that goes red when a live surface is not on the latest tag (#1711)
• README: aarch64 builds and boots from source; releases do not carry aarch64 artifacts yet (vms-0ad0) (#1713)
• vms-aae: DEFINE, ASSIGN and DEASSIGN take /TABLE=name and reach the executive's own tables (#1710)
• roadmap: reconcile after V0.7-10; in-tree notes regenerated from the tag (21 commits); compat surface regenerated (#1709)
• cluster-demo-nodeB: identity read in-step; prove the disk standalone, then inject the non-voting identity (#1708)
• vms-94a: a clusterwide logical-name database this node cannot decode still closes the member's transaction, and this node declares its own tables short (#1707)
• cluster demo: build Node B from the ref under test; the gate fails a stale OVMX node (#1706)