Wondering how to migrate solusvm to proxmox? We can help you.
As part of our Server Management Services, we assist our customers with several Promox queries.
Today, let us see how our Support Techs assist with migration.
How to migrate solusvm to proxmox?
Today, let us see the steps followed by our support Techs to perform above migration.
Convert KVM RAW Format & Migrate Proxmox VM
To convert KVM RAW format to the SolusVM LVM and migrate the Proxmox VM into SolusVM:
1. Firstly, shut down the respective Proxmox VM.
2. As an additional precaution, make a copy of the Proxmox VM (cp will do).
3. If the Proxmox VM is not in a raw format, you need to convert it using qemu-img:
qemu-img convert PROXMOX_VM_FILE -O raw OUTPUT_FILEProxmox usually stores the image files under /var/lib/vz/images/ID.
4. Create a KVM VM with no OS on the Solus node with a disk size at least as large as the raw file of the Proxmox VM (and possibly adjust settings such as the driver, PAE, etc.), and keep it shut down.
5. In the config file (usually under /home/kvm/kvmID) of the newly created Solus VM, check the following line and make a note.
<source file=’/dev/VG_NAME/kvmID_img’/>6. Then, add the Proxmox raw image over to the Solus node:
dd if=PROXMOX_VM.raw | ssh [options] user@solus_node 'dd of=/dev/VG_NAME/kvmID_img'7. Finally, boot the new Solus KVM VM.
Common issues when you migrate solusvm to proxmox:
- Size of the VM
We have often noticed issues with the migration due to issues with the size of Proxmox VM.
There could small difference between the size of the image and the size of the proxmox VM required.
If we go with the exact size of the image,it can trigger errors during migration.
Thus it would be always better to use a VM slightly greater than the size of the VM.
- Booting from Hard Disk
VMs are online and when we do a Rsync to the other server and start them up you get “Booting from Hard Disk” error on proxmox after create duplicate KVM VM.
We can fix this by stopping VM before we do rsync.
To stop the VM from CLI we log in to the host node.
Then, find the VMID using the below command.
cat /etc/pve/.vmlistOnce we get the ID we use the below command to stop the virtual machine.
qm stop <vmid>[Need help with the solution? We’d be happy to assist]
Conclusion
Today, we saw how our Support Techs Migrate solusvm to proxmox and also fixes for commonly caused issues.
0 Comments