Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Migrate solusvm to proxmox – How to do it.

by | May 28, 2021

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_FILE

Proxmox 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] [email protected]_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/.vmlist

Once 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]



Today, we saw how our Support Techs Migrate solusvm to proxmox and also fixes for commonly caused issues.






Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.