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)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).