SolusVM alternative: what moves today
KLYRN VM reads SolusVM 2 estates and takes over KVM hosts in place. What that means if you still run SolusVM 1, and the order to move in.
The short answer
KLYRN VM is a panel for selling KVM virtual machines. It takes over SolusVM 2 hosts while their machines keep running. The SolusVM 2 post covers that path step by step.
This post is for the other case. You searched for a SolusVM alternative and you are not sure which SolusVM you have.
Which SolusVM you run
SolusVM 1 and SolusVM 2 are different products with different APIs. KLYRN VM talks to the SolusVM 2 API. It does not use the SolusVM 1 API at all.
So a SolusVM 1 estate cannot be read or taken over by KLYRN VM today. We would rather say that here than have you find out after an install.
If you run SolusVM 1
You can still start with KLYRN VM beside it. Install the controller on its own server and add a new KVM node. New customers go there while the old hosts keep running.
Moving existing SolusVM 1 machines needs a planned move with downtime, because there is no takeover in place. Treat each machine as a fresh build plus a data copy.
If you plan to move to SolusVM 2 first anyway, the takeover path opens after that.
If you run SolusVM 2
KLYRN VM reads your hosts, servers, plans, addresses and customers. Every request is a read. Then the agent takes over one host at a time, with no guest restart and no new addresses.
Customers get a link to choose a new password. Until you finish a host, handing it back to SolusVM 2 is one click.
A host whose machines use VLAN tags is not taken over yet. OpenVZ is not supported, because KLYRN VM manages KVM only.
What it costs
The first compute node is free, with every feature and no time limit. Each node after it is $5 a month. A server you only read for a migration does not count. The pricing page has the detail.
Next step
Install the controller on its own server:
curl -fsSL https://get.klyrn.com/vm | sudo bash
Then read the SolusVM move page before you add the agent to any host.