Files
RedBear-OS/local/scripts
Red Bear OS 8fbf1a2066 local/scripts: add redbear-full QEMU boot test launcher (v6.0 2026)
Adds a single canonical QEMU launcher for the redbear-full desktop
target so subsequent validation runs (boot logs, init probes,
DRM/KMS registration, audio-stack bring-up, D-Bus system bus) can
be reproduced from a single script.

Coverage:
  * ACPI / GPE / Notify plumbing (acpid + kernel AML interpreter)
  * v6.0 input architecture (evdevd + virtio-keyboard / virtio-mouse)
  * MSI-X USB (xhcid via virtio xhci passthrough) and EHCI fallback
  * multi-queue NVMe (nvmed with multiple queues)
  * virtio-gpu (redox-drm via /scheme/drm/card0, opt-in via --with-gpu)
  * virtio-net (e1000d / virtio-netd via net0 user-mode networking)
  * D-Bus system bus (dbus) and redbear-sessiond
  * SDDM + KWin Wayland compositor (when redbear-full image exists)

The launcher mirrors the per-target test-*qemu.sh scripts already
in this directory (test-ps2-qemu.sh, test-greeter-qemu.sh,
test-phase4-wayland-qemu.sh) so behaviour is consistent:
q35 + OVMF, KVM opportunistic with TCG fallback, serial log to
local/docs/boot-logs/ with a timestamped filename, snapshot=on
when booting the live ISO so the build artifact is not corrupted
across re-runs.

The QEMU display is intentionally hidden (no -display gtk/vnc);
the boot log is the source of truth, not a UI surface. This
matches the v6.0 2026 NO VESA POLICY: the standard display path
is /scheme/drm/card0 via redox-drm, and the test harness never
opens /scheme/display.vesa/.

Exit code 0 on capture, exit code 1 on missing prerequisites
(firmware, qemu, image); boot outcome is in the log, not the
exit code. The 60s default timeout mirrors the redbear-mini
boot time observed in test-ps2-qemu.sh / test-timer-qemu.sh and
can be overridden with --timeout.
2026-06-09 18:18:57 +03:00
..
2026-05-29 21:59:47 +03:00