Articles
Choosing a platform: which of the seven adapters fits you
What each platform can do with the infrastructure you already have, how much each one has been tried, and three questions to ask before you decide.
About 3 min read · Last updated
In this article
Lightning VM talks to seven virtualisation platforms, but the seven are not equally mature. Most operators do not choose a platform for the sake of a panel; they look for a panel that fits the infrastructure they have. This article sums up what you get, and what you do not, with the platform you run.
Three questions
Which features will you sell? The browser console, the firewall, private networks, rate limiting, backups, personal images, ISO, migration and host evacuation exist only on VMware. If one of them is part of your product, VMware is the only choice today.
Do you need usage measurement? Usage graphs and traffic counting exist only on VMware and Proxmox. Per-server CPU measurement exists on VMware, Proxmox and Hyper-V. The idle-server insights, suspected mining, the health score and the energy report rest on that measurement.
How well-trodden a path do you want? The answer to that is below.
How much has been tried
| Platform | What the README says |
|---|---|
| VMware | Most of the testing was done with the govmomi simulator |
| Incus / LXD | Tried end to end with containers on a real Incus 6.0 server; virtual machines, LXD and clusters were not tried |
| Proxmox VE | Not yet tried on a real Proxmox server |
| XCP-ng | Not yet tried on a real pool |
| oVirt | Not yet tried on a real Engine |
| KVM (libvirt) | The scripts were tested with a mock virsh and over a real SSH server; not tried on a real host |
| Hyper-V | The least tested adapter; the PowerShell scripts were never run on a real host |
The six adapters other than VMware are called "first versions", and their tests run against mock servers that imitate the platform.
Platform by platform
VMware vSphere
Every feature is here. Creating servers needs vCenter; the firewall, private networks and rate limiting need a distributed virtual switch. You cannot sell servers on a standalone ESXi host or with the free ESXi licence.
Proxmox VE
The widest coverage after VMware: the whole lifecycle, usage graphs (once a minute) and traffic counting. The template must have the QEMU guest agent. Only the first IPv4 and the first IPv6 address are configured inside the server.
XCP-ng and oVirt
Both provide the basic lifecycle and apply all of cloud-init. There are no graphs, no traffic counting and no per-server CPU measurement. On oVirt a server cannot be cloned from another server, and the first interface in the guest must be called eth0.
Hyper-V
One host per connection; there is no Failover Cluster. The connection is WinRM over HTTPS only. There is no Windows guest customisation, which means your templates have to be Linux with cloud-init.
KVM (libvirt)
For when you have no management layer such as vCenter or Proxmox, just a plain Linux KVM host. The panel connects to the host over SSH and installs nothing. One host per connection, and only a directory-type storage pool (qcow2) is supported. To create servers the host needs virt-clone and virt-xml.
Incus / LXD
For when you want to sell both virtual machines and system containers from the same panel. The type of the image decides which one is created. It is the only new adapter that has run on a real server, but with containers only.
More than one platform
The panel manages several connections at once, and each location points at one connection. The customer chooses a location, not a platform. So you can offer a full-featured location on VMware and a plainer one on Proxmox in the same catalog. A customer who tries an operation the platform does not have sees the answer "not supported on this platform".
Deciding
If you are going to use one of the platforms other than VMware, do not open it to customers before you have tried it end to end in your own test environment. Every "not tried" line in this article leaves that work to you. The full coverage table is on the Platforms and coverage page.
