The SolusVM --> OnApp migration script will support both Windows and Linux migrations to OnApp, it should support both Xen and KVM environments. The script comes with minimal QA although we have given the script to a few clients who have helped us develop it further and resulted in successful migrations. Its important to understand that the script is only designed to migrate the virtual machine, it will not make any changes inside the virtual environment so any issues at that level that prevent the VM from booting once migrated need to be fixed manually.
A common issue after the migration that prevents the VM from booting can be fixed using the information provided in this article from Microsoft:
A common network issue with Windows VMs post migration has been fixed by our Windows L3 technical support, I'll provide details below.
1. Login to the relevant hypervisor
2. Find the disk identifier in the Onapp DB, find full path to the disk on hypervisor (For example: lvscan | grep qx9wsx4a14uxqg)
Should be something like :
3. Do the following with this paths:
kpartx -p X -a /dev/onapp-yoa7hk9k1m3deg/qx9wsx4a14uxqg
Then check if new devices was created:
ls -al /dev/mapper/ | grep qx9wsx4a14uxqg
Should be something like: qx9wsx4a14uxqgX1
brw-rw---- 1 root disk 253, 34 Aug 30 11:04 /dev/mapper/qx9wsx4a14uxqgX1
4. Mount it to the temp dir:
mount -t ntfs-3g /dev/mapper/qx9wsx4a14uxqgX1 /tmp/1/
5. go to http://www.meadowcourt.org/downloads/ and download last driver version.
6. Umount temp dir:
7. Remove the partitions:
kpartx -p X -d /dev/onapp-yoa7hk9k1m3deg/qx9wsx4a14uxqg
8. start up VM .
9. run installation and set correct IP address, netmask, gateway etc.
Please sign in to leave a comment.