# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-processmission-oh-my-qemu-qemu-direct-linux-boot`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [processmission](https://agentstack.voostack.com/s/processmission)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [processmission](https://github.com/processmission)
- **Source:** https://github.com/processmission/oh-my-qemu/tree/main/.agents/skills/qemu-direct-linux-boot
- **Website:** https://processmission.github.io/oh-my-qemu/

## Install

```sh
agentstack add skill-processmission-oh-my-qemu-qemu-direct-linux-boot
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# QEMU Direct Linux Boot

Use this workflow when QEMU should load a kernel directly, usually with `-kernel`, `-dtb`, `-initrd`, and `-append`.

## Primitive Composition

1. Use `qemu-flow-plan`.
2. Use `qemu-source-provenance` for kernel, DTB, initrd, rootfs, and QEMU binary.
3. Use `qemu-boot-run` to construct and run the command.
4. Use `qemu-model-verification` to report the boot milestone.
5. Use `qemu-debug` if 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](https://github.com/processmission)
- **Source:** [processmission/oh-my-qemu](https://github.com/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.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-processmission-oh-my-qemu-qemu-direct-linux-boot
- Seller: https://agentstack.voostack.com/s/processmission
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.