ov-foundation/skills/qemu-guest-agent/SKILL.md
QEMU guest agent for host-guest communication in virtual machines. Use when working with QEMU/KVM VMs, guest agent setup, or libvirt channel configuration.
npx skillsauth add overthinkos/overthink-plugins qemu-guest-agentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Install files | layer.yml |
qemu-guest-agent (RPM) -- QEMU guest agent daemon# image.yml -- typically used via bootc-base composition
my-vm-image:
bootc: true
layers:
- bootc-base
Part of the bootc-base composition layer. Used transitively in bootc/VM images.
The layer contributes a raw libvirt XML snippet that the libvirt renderer places in the VM's <devices> section:
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
</channel>
Emitted in layer.yml as:
libvirt:
snippets:
- "<channel type='unix'><target type='virtio' name='org.qemu.guest_agent.0'/></channel>"
This is the / classification case: isDeviceElement flags it as device-scoped, so the renderer injects it inside <devices> rather than before </domain>. See /ov-dev:libvirt-renderer for the injection pipeline and /ov-advanced:vm for the QEMU-user-net caveat (the agent shows as enabled/inactive under ov's QEMU backend; libvirt backend activates it).
/ov-foundation:bootc-base -- composition that includes this layer/ov-coder:sshd -- SSH server (also in bootc-base)/ov-foundation:bootc-config -- bootc system config (also in bootc-base)Use when the user asks about:
org.qemu.guest_agent.0 channel/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations, libvirt.snippets:)/ov-advanced:vm — VM lifecycle; bootc VM caveats; QEMU-user-net limitation/ov-vms:vms — kind: vm entity schema that consumes this layer's contribution/ov-dev:libvirt-renderer — renderer that injects this layer's snippet into <devices>/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.