Qemu Direct Linux Boot
Use for booting Linux directly with QEMU kernel, DTB, initrd, append, serial console, root filesystem, timeout, and shell markers, without traversing firmware or bootloader stages.
Install
$ agentstack add skill-processmission-oh-my-qemu-qemu-direct-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-direct-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 Direct Linux Boot
Use this workflow when QEMU should load a kernel directly, usually with -kernel, -dtb, -initrd, and -append.
Primitive Composition
- Use
qemu-flow-plan. - Use
qemu-source-provenancefor kernel, DTB, initrd, rootfs, and QEMU binary. - Use
qemu-boot-runto construct and run the command. - Use
qemu-model-verificationto report the boot milestone. - Use
qemu-debugif the run hangs or faults.
Inputs to Confirm
- QEMU binary and machine name;
- CPU, SMP, memory, accelerator, and machine properties;
- kernel image type expected by the target architecture;
- DTB path or generated FDT policy;
- initrd or block rootfs path;
- kernel command line, especially
console=,root=,rdinit=,init=, and early console settings; - expected marker, such as a shell prompt, init banner, or workload output.
Command Rules
- Keep the command copy-pasteable.
- Route serial output deterministically, usually with
-nographic. - Include a timeout for non-interactive smoke tests.
- Store the full console log under
build/agent//logs/. - When the goal is an interactive shell, provide the exact command separately from the timed smoke command.
Success Criteria
Direct boot success should name the marker reached. Examples: kernel decompressed, init started, initramfs shell, login prompt, workload completed. Do not claim the board model is correct from a banner alone.
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.