Skip to content

VelaOS 2.2 — Runtime/QEMU Development Preview

Pre-release
Pre-release

Choose a tag to compare

View all tags
@FrySco19 FrySco19 released this 11 Oct 18:02
v2.2-runtime-preview
277e46a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

VelaOS 2.2 is a public development preview, not an installable desktop OS or a security-qualified release.

Assets

  • velaos-qemu-loader.img — AArch64 seL4/Microkit QEMU demonstration image, built and smoke-tested by post-merge CI on 277e46ad9273bf6a8a8c81e7820c534f80c67746.
  • velaos-qemu-loader.img.sha256 — SHA-256 checksum for the image.

SHA-256: 7871165742d153981b040b3a7fab4b4f6dfd28496eea418e02ad3d2af3ffc33d.

Verify and boot (WSL/Linux)

Download both assets above into the same directory. Install QEMU if necessary, verify the image, then boot it:

sudo apt install qemu-system-arm
sha256sum -c velaos-qemu-loader.img.sha256
qemu-system-aarch64 \
  -machine virt,virtualization=on \
  -cpu cortex-a53 \
  -m 2G \
  -nic none \
  -serial mon:stdio \
  -nographic \
  -device loader,file=velaos-qemu-loader.img,addr=0x70000000,cpu-num=0

Exit QEMU with Ctrl+A, then X. The release image is not pcb-root.img, which is the separate Gate C root-task proof. The same command and details are in the repository README.

Benchmark status

The strict <250 ms intent-routing maximum remains not met. The latest 20-round ready-model run had one 264.2297 ms sample on a route-cache miss; p95 was 163.4565 ms. This was local inference timing, not QEMU emulation overhead. A separate 6,000-hit cache authorization microbenchmark performed fresh Biscuit validation on each hit (p95 0.2565 ms, max 0.6014 ms); no authorization bypass was implemented.

The <1.5 GB total OS idle RAM target is not qualified. The QEMU guest's LFS state is volatile, and complete Gate B–G integration/security qualification remains open.

Assets 4
Loading