Skip to content

v0.2.0 — The bundle checks itself

Latest

Choose a tag to compare

@github-actions github-actions released this 26 Oct 16:46

A bootable QEMU machine that fuses Asterinas 0.19.0 (Safe-Rust framekernel,
Linux-ABI compatible) with sixos + infuse.nix (s6 / s6-rc instead of systemd
and instead of the NixOS module system) and Lix 2.94.2 as the
system-default nix. None of the three upstream trees is forked or patched.

v0.1.0 proved the pieces run together. This release is about the layers around
that proof: the machine now shuts itself down, the state disk decides what the
next boot starts, there is documentation for installing, upgrading and rolling
back, and a release can no longer attach an archive nobody has booted.

  • The release archive is booted before it is published. scripts/smoke-bundle.sh
    unpacks the bundle a release attaches, starts that, waits for ssh, runs a
    command in the guest, and requires the machine to power itself off. The
    release workflow runs it before gh release create, so a bundle that cannot
    come up, or cannot shut down, fails the tag instead of becoming a download.
    Reproduce it on any machine with qemu, e2fsprogs and openssh:

    ./scripts/smoke-bundle.sh dist/dictyonos-v0.2.0-x86_64-qemu.tar.zst
  • poweroff -f ends the machine. The kernel writes to isa-debug-exit,
    QEMU exits with status 33, and the launcher reports that as a poweroff
    instead of sitting until TIMEOUT. QEMU failures it cannot translate are
    now passed through as failures rather than mistaken for a clean shutdown.

  • The state disk decides which configuration boots. scripts/dictyonos-switch
    records generations on the state disk (nextboot, and the prevboot it
    replaced), and stage 1 starts the recorded one; dictyonos.rollback=1 puts
    prevboot back in front for one boot. The second boot of the acceptance is
    the proof: its kernel command line still names the image's configuration, and
    the recorded generation wins.

  • docs/INSTALL.md. Installing, upgrading, rolling back, recovering, and
    the disk-space and durability limits, written against what stage1-init.sh
    actually does.

  • Asterinas moved from pin 26cb04660e to 3ed4fc4374 (the commit after
    v0.19.0-13, now v0.19.0-35-g3ed4fc437; 22 commits, 33 files, +630/-174),
    unmodified, with the whole acceptance re-run on it. Of those commits the ones
    this machine can see: supplementary groups in DAC checks, fallocate on
    O_DIRECT files, a lock fix in UNIX datagram bind, set_tid_address, and
    PVH boot parsing VMM records without assuming alignment. The kernel's
    Cargo.lock, the toolchain and the vendor hash did not change, so the
    kernel is a source swap and nothing else.

  • QEMU CPU model follows the accelerator: host under KVM,
    Icelake-Server,+x2apic,+vmx under TCG. CPU= still overrides both.
    Previously the TCG default was set before the branch, so KVM never got
    host.

  • The bundle also carries ACCEPTANCE.md and flake.lock, and CI caches its
    build, so a release is assembled from a cache instead of from nothing.

This is a proof of concept, not a distribution: there is no installer, no
security response process, no INET wildcard bind, no background writeback (the
state disk is committed by a 30-second sync -f /var), and a repairing
e2fsck would damage the state disk. /dev/ptmx is still a symlink this
image has to create, because Asterinas' devpts only publishes the master at
/dev/pts/ptmx. The full list is in README.md and docs/INSTALL.md.

The transcripts in ACCEPTANCE.md were captured on the bundle's own pin: two
boots against one state disk, the host-side e2fsck -fn and debugfs reads,
and the rollback boot in CI. AUTO=1 nix run reproduces them from source.

git clone https://github.com/LinTrau/dictyonos
cd dictyonos
nix run

Requires Nix with flakes enabled; QEMU and everything else comes out of the
flake. The prebuilt archive on this release needs only qemu, e2fsprogs and
openssh.