KVM + Cockpit — Notes from Real Use
First look
KVM has been part of the Linux kernel for a long time. It turns a normal Linux box into a hypervisor without extra software. Performance is usually close to bare metal. The tricky part is management: by default you get libvirt and command-line tools, which are powerful but not always friendly. That’s where Cockpit helps. It’s a lightweight web console that shows VMs, graphs of CPU/memory, and lets you control the host through a browser.
How it actually works
– KVM uses CPU virtualization (Intel VT-x, AMD-V) to run guests. QEMU handles emulation. Together with libvirt, admins can define, start, or stop VMs.
– Cockpit runs as a daemon on the host and exposes a web UI at port 9090. With the “machines” plugin enabled, you see VM lists, can attach ISO images, tweak resources, or shut down instances.
– Multiple hosts can be connected, but in practice many use it per-server.
The combo is good when you want the power of Linux virtualization but prefer to glance at a dashboard instead of parsing CLI output every time.
Technical profile
| Area | Details |
| Hypervisor | KVM (part of Linux kernel) |
| Management tools | libvirt, virsh, Cockpit web UI |
| Supported hosts | Linux distributions (RHEL, Ubuntu, Debian, Fedora, SUSE) |
| Guest OS | Linux, Windows, BSD variants |
| Storage | qcow2, raw images, LVM, NFS, iSCSI |
| Networking | Linux bridge, macvtap, Open vSwitch |
| License | Open source (GPL/LGPL) |
| Extra modules | Cockpit plug-ins for storage, networking, containers |
Setup notes
– Enable virtualization in BIOS.
– Install qemu-kvm, libvirt, cockpit, and cockpit-machines.
– Start services: systemctl enable –now libvirtd cockpit.socket.
– Open a browser: https://host:9090.
– Use the “Virtual Machines” tab to add or manage VMs.
Where it fits well
– Small data centers or labs where Linux is already the base OS.
– Admins who don’t want to manage VMs only from command line.
– Remote servers that need a simple dashboard view of load and VM state.
– Mixed test environments with Windows and Linux guests.
Limits to expect
– Cockpit is light; it doesn’t give cluster-wide orchestration.
– For big farms, you’ll need OpenStack, oVirt, or Proxmox.
– Some features differ by distribution since Cockpit modules aren’t uniform everywhere.
– Heavy workloads may need extra tuning of I/O and storage backends.
Comparison snapshot
| Tool | What stands out | Typical use |
| KVM + Cockpit | Native Linux virtualization + web UI, free | Small to mid Linux hosts |
| Proxmox VE | Full stack, clustering, backup tools | SMBs, labs |
| oVirt | Enterprise KVM management | Larger Linux shops |
| VMware vSphere | Broad feature set, enterprise HA | Enterprises with VMware legacy |