Skip to content
Lightning VMBeta

Features

Platforms and coverage

The seven virtualisation platforms: how the panel connects to each, what works on which, and which of them has been tried on real hardware.

Seven platforms, one contract

The panel talks to each platform through a separate adapter service, and all adapters implement the same contract. Not all of them do everything: an operation an adapter does not support ends with the error "not supported on this platform". Only VMware has every feature.

OperationVMwareProxmox VEXCP-ngoVirtHyper-VKVMIncus / LXD
Discovery, capacity, topologyyesyesyesyesyesyesyes
Create from template, reinstallyesyesyesyesyesyes ¹yes
Power on, off, restart, deleteyesyesyesyesyesyesyes
Resizeyesyesyes ²yesyes ²yes ²yes ²
Snapshotsyesyesyesyesyesyesyes
Extra disksyesyesyesyesyesyesyes
Adopt an existing VMyesyesyesyesyesyesyes
Root password, app install (cloud-init)yesvia guest agent ³yesyesyesyesyes
Usage graphsyesyesnonononono
Traffic counting and quota warningyesyesnonononono
Per-server CPU measurementyesyesnonoyesnono
Browser consoleyes ⁴nononononono
Firewall, private network, rate limitingyes ⁵nononononono
Backups, personal images, ISOyesnononononono
Migration and host evacuationyesnononononono
Tried on a real server?mostly the simulatornononononoyes: Incus 6.0, containers only
  1. If the host has virt-clone and virt-xml; without them the connection serves inventory and power operations only.
  2. With the server powered off; the panel shuts it down and starts it again itself.
  3. Proxmox's own cloud-init carries only the network and the SSH keys; the rest is applied through the QEMU guest agent.
  4. The VMware HTML Console SDK is not in the repository, and the console was not tried with the real SDK.
  5. Needs a distributed virtual switch (vSphere Distributed Switch).

VMware vSphere

You connect with the address of a vCenter or an ESXi host, a user and a password; the TLS certificate is verified by its thumbprint. vCenter / ESXi 6.0 to 9.x are supported. Creating servers needs vCenter; a standalone ESXi host offers only read and power operations, and with the free ESXi licence the API is read-only. On vCenter 7.0 U3 and later the built-in cloud-init is used, on older versions guestinfo. The panel can scan an IP block to find the ESXi hosts and vCenters on a network; no user name or password is sent during the scan.

Most of the testing was done with the govmomi simulator; a real vCenter / ESXi may behave differently. docs/vmware.md (Turkish)

Proxmox VE

A node or a cluster, 7.x to 9.x. You connect with the web interface's address and port 8006, with a user or an API token. The docs recommend a separate user for the panel and an API token without privilege separation. It is a first version and has not yet been tried on a real Proxmox server. docs/proxmox.md (Turkish)

XCP-ng / XenServer

You connect with the address of the pool master. The panel attaches a small configuration disk to every new server, and cloud-init reads its settings from that disk. A first version; not yet tried on a real pool. docs/xcpng.md (Turkish)

oVirt / RHV

Talks to the Engine's REST API; version 4.4 and later. The first network interface in the guest must be called eth0, otherwise the server gets no address. A server cannot be cloned from another server. A first version; not yet tried on a real Engine. docs/ovirt.md (Turkish)

Microsoft Hyper-V

Windows Server 2016 and later. The adapter runs PowerShell on the host over WinRM and connects over HTTPS only. One host per connection (no Failover Cluster); there is no Windows guest customisation. According to the README this is the least tested adapter: the PowerShell scripts have never been run on a real Hyper-V host. docs/hyperv.md (Turkish)

KVM (libvirt)

A plain Linux host with nothing but libvirt and QEMU/KVM on it. The adapter connects over SSH and runs virsh; it installs no agent and no package on the host. One host per connection, and storage is a directory-type pool (qcow2) only. A first version; not yet tried on a real libvirt/KVM host. docs/libvirt.md (Turkish)

Incus / LXD

Incus 6.x and LXD 5.x; virtual machines and system containers. Which of the two is created depends on the type of the chosen image. The API is reached with a client certificate. Tried end to end with containers on a real Incus 6.0 server; virtual machines, LXD and clusters were not tried. docs/incus.md (Turkish)

If you are deciding which one to use, the article Choosing a platform may help.