Self-Hosted KVM Web Management: WebVirtCloud vs Kimchi vs Cockpit Machines

Introduction

Managing KVM (Kernel-based Virtual Machine) hosts through the command line is powerful but becomes unwieldy as your virtualization footprint grows. A web-based management interface gives you visibility into all your VMs, enables team collaboration, and provides point-and-click provisioning without SSH-ing into each host. This guide compares three leading open-source KVM web management platforms: WebVirtCloud, Kimchi, and Cockpit Machines.

Each tool approaches KVM management differently — from full multi-tenant cloud platforms to lightweight single-host dashboards. We compare their architectures, deployment models, feature sets, and ideal use cases to help you choose the right fit for your infrastructure.

Comparison Table

WebVirtCloud

WebVirtCloud is a full-featured, multi-tenant KVM management platform designed for service providers and organizations managing multiple hypervisors. Built on Django with libvirt as the backend, it provides a complete cloud-like experience for KVM infrastructure.

Key strengths:

• Multi-node clustering with centralized management
• Role-based access control for team environments
• REST API for automation and integration
• Built-in VM live migration between hosts
• Support for storage pools (LVM, directory, NFS, iSCSI, Ceph RBD)

Installation (Ubuntu/Debian):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25

# Install dependencies
sudo apt update
sudo apt install -y qemu-kvm libvirt-daemon-system libvirt-clients   bridge-utils virt-manager python3-venv python3-pip nginx

# Clone and set up WebVirtCloud
git clone https://github.com/retspen/webvirtcloud.git
cd webvirtcloud
sudo ./install.sh

# Or use Docker Compose
cat > docker-compose.yml << 'EOF'
version: "3.8"
services:
  webvirtcloud:
    image: retspen/webvirtcloud:latest
    ports:
      - "8080:80"
    volumes:
      - webvirtcloud_data:/var/www/webvirtcloud
      - /var/run/libvirt/libvirt-sock:/var/run/libvirt/libvirt-sock
    restart: unless-stopped
volumes:
  webvirtcloud_data:
EOF
docker-compose up -d

WebVirtCloud excels in environments where multiple administrators need to manage VMs across several physical hosts, making it the go-to choice for small to mid-size cloud deployments.

Kimchi

Kimchi (Korea Multimedia Cloud Hypervisor Interface) was originally developed by IBM as a lightweight HTML5-based management tool for KVM. Now a community project, it focuses on providing a clean, simple interface for single-host VM management through the Wok framework.

Key strengths:

• Extremely lightweight — minimal resource overhead
• Clean, responsive HTML5 interface with noVNC console access
• Simple template-based VM provisioning
• Built-in storage pool and network management
• Supports Fedora, RHEL, CentOS, Ubuntu, and Debian

Installation (Ubuntu/Debian):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12

# Add Kimchi repository
wget -O /etc/apt/sources.list.d/kimchi.list   https://raw.githubusercontent.com/kimchi-project/kimchi/master/contrib/DEB/kimchi-deb.list
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0x95BD4743
sudo apt update

# Install Wok and Kimchi
sudo apt install -y wok kimchi

# Start services
sudo systemctl enable --now wokd

# Access at https://<your-server-ip>:8001

VM template example (Ubuntu 24.04):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

# Create a template from the Kimchi web interface
# Or via the REST API:
curl -k -u admin:password -H "Content-Type: application/json"   -H "Accept: application/json"   -X POST -d '{
    "name": "ubuntu-2404",
    "os_distro": "ubuntu",
    "os_version": "24.04",
    "source_media": {
      "type": "netboot",
      "url": "http://archive.ubuntu.com/ubuntu/dists/noble/main/installer-amd64/"
    },
    "memory": 2048,
    "cpus": 2,
    "disks": [{"size": 20}]
  }'   https://localhost:8001/plugins/kimchi/templates

Kimchi is ideal for homelab users and small deployments where a single KVM host needs a friendly web interface without the complexity of a full cloud management platform.

Cockpit Machines

Cockpit is Red Hat’s web-based server management interface, and the Machines plugin adds KVM virtual machine management capabilities. It integrates directly with systemd, providing a familiar experience for Linux administrators already using Cockpit for system monitoring.

Key strengths:

• Tight integration with Cockpit’s existing server management dashboard
• Uses system authentication — no separate user database
• Lightweight — included in base Cockpit installation
• Supports VM creation, editing, console access, and monitoring
• Actively maintained with regular updates

Installation (Ubuntu/Debian):

1
2
3
4
5
6
7
8

# Install Cockpit and the Machines plugin
sudo apt update
sudo apt install -y cockpit cockpit-machines qemu-kvm libvirt-daemon-system

# Enable and start Cockpit
sudo systemctl enable --now cockpit

# Access at https://<your-server-ip>:9090

VM provisioning via CLI (complements the web UI):

1
2
3
4
5
6
7
8

# Create a storage pool
sudo virsh pool-define-as default dir - - - - "/var/lib/libvirt/images"
sudo virsh pool-build default
sudo virsh pool-start default
sudo virsh pool-autostart default

# Create a VM via Cockpit or virt-install
sudo virt-install   --name ubuntu-server   --ram 4096   --vcpus 2   --disk pool=default,size=30,format=qcow2   --os-variant ubuntu24.04   --network bridge=virbr0   --graphics vnc,listen=0.0.0.0   --noautoconsole   --location 'http://archive.ubuntu.com/ubuntu/dists/noble/main/installer-amd64/'

Cockpit Machines is the best choice if you already use Cockpit for server administration and want a unified dashboard for both system monitoring and VM management on a single host.

Virtual Network Configuration Comparison

One key differentiator is how each tool handles virtual networking. Here’s a practical comparison of network bridge setup:

WebVirtCloud — multi-host virtual network:

1
2
3
4

# Create a bridge on each host
sudo nmcli connection add type bridge ifname br0
sudo nmcli connection add type ethernet slave-type bridge   con-name bridge-br0 ifname eno1 master br0
# Then manage virtual networks through WebVirtCloud's UI

Kimchi — single-host bridge network:

1
2
3
4
5

# Kimchi automatically manages libvirt's default NAT network
# For bridged networking, configure through the UI or:
sudo virsh net-define /tmp/bridge-network.xml
sudo virsh net-start bridge-network
sudo virsh net-autostart bridge-network

Cockpit Machines — leverages systemd-networkd:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

# /etc/systemd/network/25-bridge.netdev
[NetDev]
Name=br0
Kind=bridge

# /etc/systemd/network/30-bridge.network  
[Match]
Name=br0

[Network]
DHCP=yes

Why Self-Host Your KVM Management?

Running your own KVM management platform offers significant advantages over vendor-locked virtualization solutions. First, you maintain full ownership of your VM data and metadata — no vendor can suddenly change pricing, deprecate features, or discontinue the service. Your VM configurations, network topologies, and access controls remain under your direct control on hardware you own.

Second, the cost structure is fundamentally different. While VMware and other commercial hypervisors charge per-socket or per-core licensing fees that scale linearly with your hardware, KVM with a web management layer costs nothing beyond your server hardware and electricity. For a homelab with a single server, the savings are modest; for a small data center with 10+ nodes, they’re transformative.

Third, KVM management tools integrate with the broader open-source ecosystem. You can pair WebVirtCloud with Prometheus for monitoring, Grafana for dashboards, and Ansible for automation — building a complete infrastructure management stack without proprietary lock-in. For details on KVM-based virtualization platforms, see our comprehensive comparison of Proxmox, XCP-ng, and oVirt.

If you’re managing servers remotely without physical access, our IP-KVM solutions guide covering PiKVM, TinyPilot, and BlikVM complements these web management tools with out-of-band access capabilities. For organizations running Kubernetes alongside traditional VMs, our KubeVirt vs Harvester vs OpenNebula comparison explores platforms that bridge container orchestration and VM management.

FAQ

Which KVM web manager should I use for a single-server homelab?

For a single-server homelab, Cockpit Machines is often the best choice. It’s lightweight, already integrated with Cockpit (which you’re likely using for system monitoring), and requires minimal configuration. If you want more polished VM management with template support and storage pool management, Kimchi offers a clean, focused interface. Both work well on a single host.

Can WebVirtCloud manage VMs across different physical servers?

Yes — WebVirtCloud is specifically designed for multi-node KVM management. It supports clustering multiple hypervisors under a single management interface, with features like centralized user management, VM live migration between hosts, and unified storage pool management. This is its primary advantage over Kimchi and Cockpit Machines.

Is Kimchi still actively maintained?

Kimchi’s main repository last saw updates in January 2023, making it the least actively maintained of the three. However, it remains functional and stable for basic KVM management on supported distributions (Fedora, RHEL/CentOS, Ubuntu, Debian). For new deployments, Cockpit Machines or WebVirtCloud may be preferable for ongoing support and feature updates.

Do these tools support GPU passthrough for VMs?

All three tools can configure GPU passthrough since they ultimately interface with libvirt, which supports PCI passthrough. However, the ease of configuration varies. WebVirtCloud provides the most GUI options for PCI device assignment. With Kimchi and Cockpit Machines, you typically need to configure passthrough manually via virsh edit or by editing the VM XML directly, then use the web interface for day-to-day management.

How do these compare to Proxmox VE?

Proxmox VE is a complete virtualization platform that includes its own kernel, storage system (ZFS), clustering, and web interface — it replaces the host OS rather than just providing a management layer on top of an existing Linux installation. The tools compared here are management interfaces for KVM on a standard Linux distribution (Ubuntu, Debian, Fedora, RHEL). Choose Proxmox if you want an all-in-one appliance; choose these tools if you prefer to run KVM on your distribution of choice with a web management layer added on top.

💰 想测试你的市场判断力？我用 Polymarket 做预测市场交易——这是全球最大的预测市场平台，从大选结果到技术监管时间线，什么都可以押注。和赌博不同，这是真正的信息市场：你懂的信息越多，胜率越高。我靠预测技术相关事件的走向已经赚了不少。用我的邀请链接注册：Polymarket.com