What is SPICE?
SPICE lets you see and control a virtual machine's screen, keyboard and mouse from a client program on another computer. It was developed by Qumranet and released as open source by Red Hat after Red Hat acquired that company. It is most closely tied to the Linux KVM/QEMU virtualization stack.
How it works
- Server: built into QEMU on the virtualization host, so the console is served from the hypervisor side, not by software running inside the guest.
- Client: a viewer such as
remote-viewer(part of virt-viewer) on the technician's machine connects to the host. - Guest components: the QXL paravirtual video driver and the SPICE guest agent (
spice-vdagent) add clipboard sharing, automatic display resizing and smoother mouse handling.
Other features include USB redirection (plug a device into the client and pass it through to the VM), audio playback and recording, multiple monitors and TLS encryption of the connection. On libvirt-based hosts, console connections are usually accepted only from the host itself by default; remote access has to be opened deliberately and should be protected with a password or TLS.
Where you see it
- virt-manager and GNOME Boxes on Linux desktops
- Proxmox VE, which offers a SPICE console as an alternative to its browser-based noVNC console
- oVirt and other KVM-based server and desktop virtualization platforms
SPICE vs. other remote access protocols
| Protocol | Runs where | Notes |
|---|---|---|
| SPICE | Hypervisor (QEMU) | VM consoles with USB redirection and audio; works before the guest OS boots |
| VNC | Hypervisor or guest OS | Simple, widely supported screen sharing; TCP 5900 by default |
| RDP | Inside the Windows guest OS | Microsoft protocol on TCP 3389; needs the guest booted and on the network |
| SSH | Inside the guest OS | Encrypted command line on TCP 22; no graphical desktop |
The practical difference: because SPICE is served from the host, you can watch a VM's boot screen or repair a guest whose network settings are broken, in cases where RDP or SSH into the guest would fail.
CompTIA's expansion of SPICE
The CompTIA A+ Core 1 acronym list expands SPICE as Software Process Improvement and Capability Determination. That is a different thing: an ISO/IEC 15504 framework for assessing the maturity of software development processes. It has nothing to do with remote access or virtual machines.
SPICE on the CompTIA A+ exam
Recognize both expansions. In remote access and virtualization questions, SPICE means the VM display protocol. Cues:
- A remote console to a KVM/QEMU or Proxmox virtual machine with USB redirection: SPICE.
- A remote session to a running Windows desktop on port 3389: RDP, not SPICE.
- A command-line session to a Linux server on port 22: SSH.
- Clipboard sharing or automatic resizing doesn't work in a SPICE console: the guest agent is missing or not running in the VM.
- An option that spells out Software Process Improvement and Capability Determination is using the acronym-list wording.