Migration from other panels

KoaVM moves VMs from other panels to the Incus nodes keeping the same IP and MAC, cold or near-live (about 10 seconds of downtime).

Sources

In Migration › Connect a source: SolusVM 1, SolusVM 2, Virtualizor, Proxmox VE or any KVM/libvirt node.

• Nodes (required): the addresses of the servers where the VMs run, with root or a user with passwordless sudo. The panel reads them over SSH with its key.
• Panel API (optional): adds hostname, IP and customer of each VM and, after the move, suspends the VM in the old panel.

Add the panel key (on the Migration page) to authorized_keys on the source nodes and on the destination Incus nodes. The Incus nodes need qemu-utils.

How a VM moves

1. Scan: the panel finds the VMs, disks and IPs.
2. For each VM choose the customer (existing or new), the destination node and the mode.
3. Checks: before starting the panel verifies space, network, IPs and access; if something is wrong it says so and does not start.
4. Start now or at a set time, at most N migrations at once (in Settings).

The modes:

• Cold: the VM shuts down, the disk is copied, the VM starts again on Incus. Downtime equals the copy time.
• Near-live: the disk is mirrored while the VM runs, then one restart on the new node (about 10 seconds of downtime).

All the VM's disks move; ZFS, LVM, dir and btrfs storage work on Incus. A VM that is off at the source stays off.

If something goes wrong

The source VM goes back to how it was and starts again; with provider IPs the IP goes back to the previous server. The VM detail shows the error and the log of the steps.

Customer emails

With emails turned on (Settings) the customer gets a notice before and after the move, with the time and the expected downtime.