Virtualizor is one of the sources of Infrastructure › Import from another panel. The import reads the Virtualizor master through its admin API and brings over users, plans, IP pools and KVM servers in the same four-step wizard as SolusVM. Disks are copied by VMStack nodes that log into the Virtualizor hypervisors over SSH. Servers whose hypervisor the nodes cannot reach are kept as records only and moved later.
The master is only read; a server is shut down there only when you ask for a clean copy, and started again if that copy fails. OpenVZ and Xen servers are listed but not imported.
Before you start#
- API credentials. In Virtualizor's admin panel, create API credentials (an admin API key and password) and allow the VMStack panel's address.
- Network. The panel reaches the master's admin panel on TCP 4085 (HTTPS). Each VMStack node that receives servers reaches the hypervisors over SSH (TCP 22).
- SSH on the hypervisors. A user that can run
virshand read the disks (LVM volumes such as/dev/<vg>/vsv…, or qcow2 files);rootis the simple case.
Connect the master#
- Go to Infrastructure › Import from another panel › Connect a panel.
- Under The panel, choose Virtualizor, give a Name and the Address, for example
https://master.example.net:4085. - Under API credentials, enter the Admin API key and Admin API password. They are stored encrypted, never shown again and never logged.
- Optionally paste the Certificate fingerprint (optional), and set Servers copied at once (1 to 8).
- Press Save and check.
Virtualizor's certificate is usually self-signed. The check shows its SHA-256 fingerprint and sends no credentials until you compare it (openssl x509 -noout -fingerprint -sha256 -in <certificate> on the master) and press Trust this certificate…. The source then reads hypervisors, users, plans, IP pools and servers.
Map the hypervisors#
For each hypervisor listed under Hosts, press Map and SSH…, choose the VMStack node its servers go to and the SSH login, add the nodes' keys to /root/.ssh/authorized_keys on the hypervisor, press Save and check the login, and trust the host key. The steps are the same as for SolusVM: see Map the hypervisors and their SSH login.
Run the import#
Press Import… on the source. The wizard's steps (What it has, How it maps, What will happen), the dry run with its CSV, records-only servers and Move now work exactly as described in The import wizard.
Virtualizor specifics:
- Users are matched to VMStack accounts by e-mail, or created; their names are taken from Virtualizor's user preferences.
- IPv4 pools can be mapped or created on a node; IPv6 pools are created on the node's link when their prefix is known. NAT IP pools are left out, with a note.
- A server's libvirt domain on the hypervisor is its Virtualizor name (
v1001and so on); the node reads the domain's hardware (firmware, machine, disks, cards) from the hypervisor, so UEFI servers stay UEFI.
Copies are followed, cancelled and retried on Infrastructure › Imports in progress, as described for Proxmox imports.
Not imported#
OS templates, node groups and locations (VMStack's own are used), snapshots and backups, billing links, network disks, and anything that is not x86_64 KVM.