rhiannon-ai-llc/kvm-corpus (kvm-microvm-lifecycle)

Build and operate the KVM substrate a VMM's device models sit on. Use when working with the /dev/kvm file-descriptor model, KVM_CHECK_EXTENSION capability probing, guest memory slots via KVM_SET_USER_MEMORY_REGION, KVM_CREATE_GUEST_MEMFD and memory attributes, the KVM_RUN loop and its exit reasons, MMIO and PIO dispatch to device models, vCPU state save and restore, interrupt injection and GSI routing, eventfd acceleration through KVM_IRQFD and KVM_IOEVENTFD, in-kernel devices via KVM_CREATE_DEVICE, the KVM_DEV_TYPE_VFIO tracking device, dirty logging, guest clock continuity, or snapshot, restore and copy-on-write fork ordering. Also covers confidential VMs — AMD SEV, SEV-SNP, Intel TDX, Arm pKVM and s390 Protected Virtualization — and how guest-private memory invalidates device backends and snapshot schemes that assume host-readable guest RAM.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/rhiannon-ai-llc/kvm-corpus

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.

1 critical finding reported by cisco-skill-scanner. The composite score alone does not reflect this — read the per-scanner reports below.