RayNu-V Honest Distance Assessment

RayNu-V

11 September 2026 · Dell PowerEdge R640 · COM2

Mount Everest — closed on iron

The product loop is done. One EFI, a real R640, a browser on the operator LAN, a Linux ISO installed to virtio disk, and a reboot into that disk to a login prompt. COM2 printed the markers. This is the win.

Ship EFI → boot real R640 → network vSphere-like UI → deploy Linux ISO → M7 closed

Tracker · synced from docs/hda.md

Mount Everest

Closed

0.0 months remaining · summit 2026-09-11

Overall readiness
99%
ETA month
2026-09
Confidence
high
Updated
2026-09-11
Everest summit
Overall product readiness 99%

99% on purpose. Standing SPA and a guest console UI are M8 (ADR-018) — not a reopened Everest. HV-reboot persist is evidence-closed on the 8 GiB USB slice (928d6224). EFI 1fa231df halted its USB soak boot with no guest and its controller dumps showed the fault: commands completed while the driver read the 16-byte completion event pointer-first, cycle-last, and skipped its own event when the write landed mid-read. The next EFI reads the control word first as one 32-bit load.

Iron · 2026-09-11 · EFI f72b4276

What COM2 printed

iDRAC SOL console com2 on a real PowerEdge R640. UDisk front USB 2. No --raynu-f. The operator SPA started RayNu-F, Alpine installed to virtio vda, and F7 booted the installed disk. Host and CI still never print RAYNU-V-M7-ISO-INSTALL-OK — that marker is iron-only. 

build: sha=f72b4276d198
RAYNU-V-M7-PHASE-B-SKIP-OVMF-OK
RAYNU-V-M7-PHASE-B-E4-CONTINUE-OK
HOST-NIC coexist listening on 10.99.99.145:8443
RAYNU-V-M7-HOST-NIC-HTTP-OK
RAYNU-V-AUDIT: AuthAllowed method_tag=2
VmCreated guest_id=4
VmStarted guest_id=4
boot: E4 SPA start — RayNu-F product ISO (Phase B; not SHELL; not ISO-INSTALL-OK)
RAYNU-V-M7-ISO-INSTALL-OK
RayNu-F relaunch after reset (F7)
RAYNU-V-RAYNU-F-DISK-BOOT-OK
Linux version 6.12.13-0-lts
Command line: … root=UUID=814a97a0-d3be-4a64-8611-b3dbd9859201 … rootfstype=ext4
EXT4-fs (vda2): mounted filesystem 814a97a0-d3be-4a64-8611-b3dbd9859201
Welcome to Alpine Linux 3.21
localhost login: root
localhost:~# cat /proc/cmdline

Four summits — reached

Core hypervisor work was never the gap. The gap was the operator loop on iron: real R640, durable HTTP beside VMX, SPA that starts a guest firmware, a distro installer that writes a disk, and a reboot into that disk. That loop closed.

  1. Ship EFI 95% M7.0 + iron kits under releases/
  2. Real R640 boot 98% E2 closed — SHELL+M4 on COM2
  3. Network vSphere-like UI 98% E3+E3b+Phase F+P0-14+Phase B closed on iron f72b4276 (SPA Start of RayNu-F). TLS/console are M8.
  4. Deploy Linux ISO 99% Closed on real R640: Alpine ISO → virtio disk (RAYNU-V-M7-ISO-INSTALL-OK) → reboot (RAYNU-V-RAYNU-F-DISK-BOOT-OK) → second Linux root=UUID= → login

Production bar (M6.8 soak + M6.9 external): 100% on Latitude — RAYNU-V-M6-EXT-OK. Hypervisor core ~88%.

Bottom line

Mount Everest is closed on iron. M0→M7.8, E4 SPA VMLAUNCH, E5 Phase A (56a3ffd), and Phase B SPA (f72b4276 / 34552377351) printed the loop: EFI → real R640 → coexist HOST-NIC-HTTP-OK on 10.99.99.145:8443 → SPA Start of RayNu-F → Alpine setup-disk → RAYNU-V-M7-ISO-INSTALL-OK → F7 → RAYNU-V-RAYNU-F-DISK-BOOT-OK → root=UUID=814a97a0-… → login:. Latitude/QEMU still ≠ R640. Host/CI still never print ISO-INSTALL-OK. Overall stays 99% because the latest keep=1 boot still stops at the GRUB command line, and Standing SPA and a guest console UI are the next mountain — M8 operator hardening (ADR-018). TLS iron and HV-reboot persist are closed on COM2 (928d6224 printed RAYNU-V-M8-TLS-OK and RAYNU-V-M8-DISK-PERSIST-OK on the 8 GiB USB slice). Cluster / vMotion-like is M9. Rollback kit: v0.1.0-everest-closed.

Full living assessment Read the summit story

Numbers load from site/hda.json, regenerated from docs/hda.md by ./tools/sync-hda-site.sh on every HDA update. Last commit: PENDING.