phoebus_os/installer/tests/vm
Phoebus a20e064680 fix(update): keep fetched distfiles when binary prebuild is skipped
emerge --buildpkgonly refuses while dependencies still need merging, which
is normal for an out-of-date system. Record that as Ready with the fetched
distfiles and the Portage reason instead of a hard Failure, and include the
redacted stderr tail in the state note. The VM harness check timeout is now
configurable.
2026-09-20 05:00:45 -07:00
..
install.sh test(vm): drive the static Rust installer from the VM harness 2026-09-20 03:02:37 -07:00
README.md test(vm): drive the static Rust installer from the VM harness 2026-09-20 03:02:37 -07:00
run-vm.sh test(vm): drive the static Rust installer from the VM harness 2026-09-20 03:02:37 -07:00
serial-driver.py fix(update): keep fetched distfiles when binary prebuild is skipped 2026-09-20 05:00:45 -07:00
test.conf.example chore: import Phoebus OS installer and Rust migration 2026-09-20 02:07:33 -07:00

Disposable UEFI VM harness

Proves that the installer produces a bootable encrypted system without ever touching a physical disk. The target is always a qcow2 file.

Files

  • run-vm.sh interactive QEMU launcher (manual testing).
  • install.sh guest-side, non-interactive installation (run in the VM).
  • serial-driver.py host-side pexpect driver (install and boot modes).
  • test.conf.example installer configuration used by the driver.

Host prerequisites

  • qemu-system-x86_64, qemu-img, OVMF firmware, Python pexpect.
  • The reference Gentoo ISO.
  • The static Rust installer (the guest never runs the Bash tree):
cd installer-rs
RUSTFLAGS="-C target-feature=+crt-static" \
  cargo build --release -p phoebus-installer --target x86_64-unknown-linux-gnu

Procedure

Serve the static installer, the stage3 and the config to the guest:

cd /path/to/serve
cp /path/to/phoebus_os/installer-rs/target/x86_64-unknown-linux-gnu/release/phoebus-installer .
cp /path/to/phoebus_os/installer/tests/vm/install.sh .
cp /path/to/phoebus_os/installer/tests/vm/test.conf.example test.conf  # edit TARGET_DISK etc.
sha256sum stage3.tar.xz                               # set STAGE3_SHA256
python3 -m http.server 8000 --bind 127.0.0.1

Run the installation (driver boots the ISO kernel/initrd directly and drives the serial console):

QEMU_BIN=/path/to/qemu-system-x86_64 \
QEMU_LIBDIR=/path/to/qemu/libs \
QEMU_DATADIR=/path/to/qemu/share \
OVMF_CODE=/path/to/OVMF_CODE_4M.fd \
OVMF_VARS=/path/to/OVMF_VARS.fd \
DISK=/tmp/phoebus/target.qcow2 \
ISO=/path/to/livegui-amd64.iso \
KERNEL=/tmp/live/boot/gentoo INITRD=/tmp/live/boot/gentoo.igz \
INSTALL_URL=http://10.0.2.2:8000/install.sh \
python3 installer/tests/vm/serial-driver.py install

Then boot the disk alone (ISO detached) and verify:

DISK=/tmp/phoebus/target.qcow2 OVMF_CODE=... OVMF_VARS=... \
python3 installer/tests/vm/serial-driver.py boot

To patch a console into an existing entry for observation, the BLS entry in /efi/loader/entries/*.conf takes an options line; the installer can also embed a console via KERNEL_CONSOLE (GENTOO_KERNEL_CONSOLE equivalent).

Safety

  • DISK must be a qcow2 image; never point it at /dev/*.
  • The installer itself classifies the ISO's device as protected.
  • Secrets are passed through 0600 files and are checked for leakage in the installer log by install.sh.