Skip to content
VirtlixCP

Documentation / KVM Virtual Servers

Importing VPSes from Other Panels

VPS, Import moves running KVM VMs from another panel onto your hypervisors. Each VM keeps its data, MAC address and IPs, and becomes an ordinary VPS here.

Import from What the panel reads
Virtualizor VMs, hostnames, IPs, clients, OS and bandwidth from its database
SolusVM KVM VMs, hostnames, IPs, clients and OS from the master's database
Proxmox VE VMs, sizes and cloud-init IPs from each VM's settings
Virtlix VPS panel VMs, hostnames, IPs, clients and OS
Other KVM (libvirt) VMs only; IPs from the guest agent when it runs

Add the old server

  1. Open VPS, Import and press Add server.
  2. Pick the panel, then enter the server's address, SSH port, user and password. The password is used once to install the panel's own SSH key and is not stored.
  3. For Virtualizor, SolusVM or the Virtlix VPS panel, tick The panel itself runs on another server when its database is on a different machine (for example the Virtualizor master or the SolusVM master) and enter that server too.

Import

Press Show VMs. For each VM you choose:

  • the operating system, guessed from the old panel; it is used for the logo and for later reinstalls
  • Keep its IP, or give it a new IP from a pool
  • whether to add its client here; a client with the same email is used automatically

Pick the hypervisor, tick the VMs and press Import. For each VM:

  1. it is shut down on the old server
  2. its disks are copied to the hypervisor (LVM volumes, qcow2 and raw files, layered disks are joined into one)
  3. it starts here with the same MAC, disk type, network card and BIOS or UEFI setting

The old VM stays on its server, stopped and no longer started at boot, so you can go back to it. Delete it there once you are happy.

Before you import

  • Keep IP: the IP must be in one of your IP pools and routed to the new hypervisor. Add it to a pool first if it isn't.
  • New IP: the VPS gets its new IP and a new root password on its first boot here. This needs cloud-init in the VM, which most cloud images have. Windows VMs always keep their IP.
  • Passwords: an imported VPS keeps its own root password. The panel shows none until you set one with Change password, which also lets the panel manage it from then on.
  • Space: the hypervisor needs free space for the disks, about twice their size for LVM, raw or layered disks while they are converted.

If an import fails, nothing is left on the hypervisor, the IP goes back to the pool and the old VM is started again. The error shows next to the VM so you can fix it and try again.