Qemu Kernel Build
Use for building Linux kernels for QEMU boot testing, including defconfig selection, cross compile variables, Docker or host toolchains, Image, DTB, modules, initramfs inputs, output hashes, and provenance records.
Install
$ agentstack add skill-processmission-oh-my-qemu-qemu-kernel-build ✓ 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-kernel-build) 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 Kernel Build
Use this workflow when a QEMU task needs a Linux kernel artifact to boot or debug a modeled board.
Primitive Composition
- Use
qemu-flow-planfor scope, acceptance criteria, and artifact root. - Use
qemu-source-provenancebefore building. - Build the kernel with the local tree's documented method.
- Update
source-provenance.mdwith producedImage,vmlinux, DTBs, modules, initramfs inputs, and hashes. - Hand off to
qemu-direct-linux-boot,qemu-firmware-linux-boot, orqemu-image-packaging.
Build Flow
Record and verify:
- kernel source path, revision, and dirty state;
- architecture, cross compiler prefix, compiler path, and version;
- defconfig and any config fragment or manual
.configchange; - output directory, build command, and parallelism;
- DTB names and destination paths;
- module install path if modules are needed;
- initramfs or rootfs source if the boot command depends on it.
Command Shape
Use the kernel tree's preferred commands. Typical Linux patterns are:
make ARCH= O=
make ARCH= O= CROSS_COMPILE= -j$(nproc) Image modules dtbsIf Docker is used, record image, mounts, user, working directory, and the command run inside the container.
Output Rules
- Do not mix outputs from different kernel revisions without recording it.
- Hash the exact files passed to QEMU or packed into an image.
- Keep build logs under
build/agent//logs/. - If the kernel boots but modules fail to load, verify kernel release and module tree before changing QEMU.
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.