carapace-sh/carapace-bin / skills/qemu
qemu
UnverifiedUse when working with QEMU — qemu-system-*, qemu-img, qemu-nbd, qemu-storage-daemon, qemu-pr-helper, block drivers, machine types, CPU models, device emulation, networking, display options, QMP protocol, and guest agent. Triggers on: "qemu", "qemu-system", "qemu-img", "qemu-nbd", "qemu-kvm", "QEMU", "qcow2", "qcow", "qed", "virtio", "virgl", "vhost-user", "VirtIO", "block driver", "machine type", "SEV", "SEV-SNP", "TDX", "snapshot", "backing file", "NBD", "Network Block Device", "QMP", "QEMU Monitor Protocol", "guest agent", "qemu-ga", "cpu model", "host passthrough", "SPICE", "VNC".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| references/block-devices.md | markdown | 4.1 KB |
| references/block-drivers.md | markdown | 4.6 KB |
| references/cpu-models.md | markdown | 4.8 KB |
| references/devices.md | markdown | 5.1 KB |
| references/display.md | markdown | 4.2 KB |
| references/guest-agent.md | markdown | 4.0 KB |
| references/machine.md | markdown | 3.2 KB |
| references/man-docs.md | markdown | 2.9 KB |
| references/networking.md | markdown | 5.2 KB |
| references/overview.md | markdown | 3.8 KB |
| references/qemu-img.md | markdown | 6.5 KB |
| references/qemu-nbd.md | markdown | 3.3 KB |
| references/qemu-pr-helper.md | markdown | 2.0 KB |
| references/qemu-storage-daemon.md | markdown | 3.7 KB |
| references/qemu-system.md | markdown | 5.2 KB |
| references/qmp.md | markdown | 5.8 KB |
references/machine.md
View on GitHub# Machine Types
The machine type defines the motherboard/chipset, devices, and firmware interface for the VM. Use `-machine help` to list available machines for your architecture.
## x86 Machine Types
### pc-i440fx
Standard PC with Intel 440FX chipset. The original QEMU PC machine.
```
-machine pc-i440fx-11.0 # current version (alias: pc)
-machine pc-i440fx-9.0 # versioned (migration-compatible)
```
- i440FX host bridge + PIIX3 southbridge
- ISA bus (keyboard, serial, parallel, floppy, RTC via PIIX3)
- PCI bus with PIRQ routing
- Firmware: SeaBIOS (legacy BIOS) or OVMF (UEFI)
- Legacy: `-machine pc`
### pc-q35
Standard PC with Intel Q35 chipset. Modern replacement for i440FX.
```
-machine q35
-machine pc-q35-11.0
```
- Q35 MCH + ICH9 southbridge
- PCIe root bus (native PCIe)
- AHCI (SATA) on ICH9
- ICH9 integrated Intel HD Audio and GbE
- Better for modern operating systems
- Supports PCIe native hotplug
- Firmware: SeaBIOS or OVMF
### microvm
Minimal machine type. Ultra-small, no PCI, no ACPI.
```
-machine microvm
```
- No PCI bus at all
- Only virtio-mmio devices
- Device tree (DT) instead of ACPI
- Minimal firmware overhead
- Use with `-kernel`, x86 needs `-machine microvm,acpi=off` for some configs
- Good for fast boot, tiny VMs, and kata containers
### nitro-enclave
```
-machine nitro-enclave
```
AWS Nitro Enclave compatible machine. Minimal, no persistent storage, no network (except vsock). For building confidential computing enclaves.
## ARM / AArch64 Machine Types
### virt
```
-machine virt
```
- Generic ARM virtual platform
- No physical hardware correspondence
- VirtIO devices (PCIe or MMIO)
- ACPI or device tree
- UEFI boot via `-bios QEMU_EFI.fd`
### Other ARM machines
```
-machine raspi4b # Raspberry Pi 4 Model B
-machine virt-11.0 # versioned virt
-machine sbsa-ref # ARM SBSA reference (server-class)
```
## RISC-V Machine Types
### virt
```
-machine virt
```
- Generic RISC-V virtual platform
- VirtIO MMIO and PCIe
- OpenSBI firmware
## s390x Machine Types
### s390-ccw-virtio
```
-machine s390-ccw-virtio
```
- IBM S/390 channel I/O
- VirtIO via CCW (channel command word)
- No PCI (zPCI adds PCI passthrough)
- IPL from DASD or SCSI
## Versioned Machine Types
Machine types are versioned to support live migration compatibility across QEMU releases:
```
pc-i440fx-9.0 # migratable to pc-i440fx-9.x
pc-i440fx-9.2 # migratable to pc-i440fx-9.x
pc-q35-9.0 # migratable to pc-q35-9.x
```
Each release adds a new aliased version. The `pc` alias always points to the latest `pc-i440fx` version; `q35` to the latest `pc-q35`.
The `latest` (unversioned) machine type enables new features but breaks migration to older QEMU. Versioned types preserve migration compatibility within the major version range.
## Migration Compatibility
To enable live migration:
1. Both hosts must use compatible QEMU versions
2. Must use the same versioned machine type
3. CPU model must be stable across hosts (use a named model, not `host`)
4. Device configuration must match
5. Check with `qemu-system-x86_64 -machine pc-q35-9.0,usb=on` — enable needed features explicitly
## See Also
- `qemu-system-ARCH -machine help` for available machines
- [qemu-system.md](qemu-system.md) for machine properties
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |