Can VirtualBox VMs Be Imported Into Scale HC3
-
@Minion-Queen Can you all import a VM into the Scale cluster that was exported from VirtualBox?
-
@scottalanmiller ????
-
@travisdh1 said in MangoCon Speakers:
@Minion-Queen Can you all import a VM into the Scale cluster that was exported from VirtualBox?
Don't believe so. It's a different disk format and a different VM format. It's possible, but we'd have to experiment. And it might require the VBox VM to be set up for KVM or some format.
-
Tagging @scale @Aconboy @craig-theriac @davedemlow
-
@scottalanmiller Yeah, that's correct. You would have to convert the virtualbox image to qcow2 using a tool like qemu-img and then follow the steps to import (...create a VM on HC3, export it, copy over the exported qcow2 with your newly converted qcow2, import). I can't say that I have done it, but would be happy to play around with the process if it is helpful.
There are also tools like HC3 Move which would do this conversion without much downtime. For this tool you install HC3 Move in a VM running on HC3 and the source (virtualbox in your case)...it then continuously captures byte-level changes and transfers them over to HC3. Once the initial synchronization is complete, it continues replicating changes until you tell it to cut over at which point it shuts down the source and restarts the target VM on HC3.
-
If it's an .ova, you can untar it and do qemu-img convert on the .vmdk file that's inside.
-
@craig.theriac said in Can VirtualBox VMs Be Imported Into Scale HC3:
@scottalanmiller Yeah, that's correct. You would have to convert the virtualbox image to qcow2 using a tool like qemu-img and then follow the steps to import (...create a VM on HC3, export it, copy over the exported qcow2 with your newly converted qcow2, import). I can't say that I have done it, but would be happy to play around with the process if it is helpful.
There are also tools like HC3 Move which would do this conversion without much downtime. For this tool you install HC3 Move in a VM running on HC3 and the source (virtualbox in your case)...it then continuously captures byte-level changes and transfers them over to HC3. Once the initial synchronization is complete, it continues replicating changes until you tell it to cut over at which point it shuts down the source and restarts the target VM on HC3.
Do you leverage virt-p2v for this or did you guys write something proprietary?
-
@stacksofplates for HC3 Move it is actually in partnership with Vision Solutions. The full name is HC3
Move Powered by Double-Take...Double-Take Move being the product we are OEM-ing for that.We have played around with virt-v2v and virt-p2v, but haven't integrated them in the product yet.
