nvx tested by Argusic Runner

What the test found

Dependencies installed in a venv and the release bundle downloaded/verified; the Python tooling test suite passes (454 tests), OpenVMM runs its 4562-test unit suite with only the container's NUMA-seccomp-blocked mbind tests failing, the openvmm binary answers version/help, and the kernel plus all three initramfs images and the erofs layer decode as valid media; a real guest boot could not run because this container has no /dev/kvm or /dev/mshv and the shipped OpenVMM build provides no emulation backend.

No third-party keys required. Python unit suite fully green (454 tests, 7 Windows-only skips). OpenVMM unit suite runs 4562 tests; best result 4560 passed / 2 failed / 10 skipped, remaining failures are NUMA mbind (EPERM via container seccomp) and only reproducible when the NVMe test migrates to container-allowed host CPUs >=64. Guest artifacts (kernel ELF, three initramfs cpio images, erofs superblock) all decode cleanly.

Argusic installed nvx in 70 minutes and launched it; verification reached Verified with mock services. 7 of 7 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of nvx

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.