Qemu Firmware Linux Boot
Use for booting Linux through firmware or bootloader stages in QEMU, including BIOS, pflash, ROM, SPL, TPL, U-Boot, TF-A, EDK2, boot media, serial logs, timeout markers, and debug handoff.
Install
$ agentstack add skill-processmission-oh-my-qemu-qemu-firmware-linux-boot ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-processmission-oh-my-qemu-qemu-firmware-linux-boot) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
QEMU Firmware Linux Boot
Use this workflow when Linux must be reached through firmware or bootloader code rather than direct kernel loading.
Primitive Composition
- Use
qemu-flow-plan. - Use
qemu-source-provenancefor firmware, bootloader, kernel, DTB, rootfs, and QEMU. - Use
qemu-image-layoutfor boot media, pflash, ROM, or disk images. - Use
qemu-boot-runto run and log the firmware path. - Use
qemu-debugto isolate the failing stage if boot stalls. - Use
qemu-model-verificationto report the reached milestone.
Stage Checklist
Record each expected stage and marker:
- reset vector or ROM entry;
- first firmware console output;
- SPL/TPL or early loader milestone;
- trusted firmware or monitor handoff if present;
- bootloader prompt or autoboot path;
- kernel entry;
- Linux console and rootfs or shell marker.
Command Rules
- Keep firmware inputs and boot media inputs distinct in the command record.
- Record firmware environment assumptions and any interactive bootloader commands.
- Use disposable or refreshed images when firmware writes runtime state.
- Capture the entire serial log; summarize the first failing stage in
evidence.md. - If Linux uses a different console from firmware, state which QEMU chardev carries each log.
Debug Handoff
For timeouts, narrow by stage before changing source:
- add
-S -sor another gdbstub backend for guest state; - add focused QEMU log flags or trace events;
- use instruction logs only around a bounded PC window when possible;
- compare image layout and firmware inputs before assuming model behavior is wrong.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: processmission
- Source: processmission/oh-my-qemu
- License: MIT
- Homepage: https://processmission.github.io/oh-my-qemu/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.