If you are an IT guy I am sure you have used some kind of Virtualization or at least heard about it. I personally have used just about everything out there. I am sure I have missed some but here is the list I have used. Vmware, Xen, OpenVZ, Virtual Box, KVM, Virtual PC, HyperV, and Parallels. I am sure I missing some that I cannot think of right now. I have also tried and used many control panels for Virtualization Management. To list some HyperVM, SolusVM, Proxmox VE, and OnAPP. I am sure I am missing some again as I used several of Vmware’s and others… Back to the topic. I started using Proxmox a few years ago. I put a couple in the data center I worked at as they were way to cheap to buy anything. One thing I like about it is that any Virtual Host has its own cp or it can be cluster and have one cp for several servers. The next thing I like about is is it can do Online Migrations if you have a SAN. There is more I like as well. You can setup backups on a schedule. It allows you to use KVM or OpenVZ. Proxmox VE has a bunch of OpenVZ templates built it. It is easy to install you just put the cd in and go! Most of all its FREE! Being in Data Centers all the time I see it used quite often. If you want a great piece of Virtualization Technology try Proxmox VE They just released the Beta and will be releasing version 2 very soon!
I worked for a data center that hated Parallels. The wanted to stop paying the ridiculous pricing for Virtuozzo.. We decided to migrate from Virtuozzo to OpenVZ. We were actually going to SolusVM but the migration to any OpenVZ platform should be the same.
First you should copy over the configuration file. We like to do this using rsync.
rsync -a -e ssh /vz/private/1234/ve.conf firstname.lastname@example.org:/etc/sysconfig/vz-scripts/6860.conf
Next we copy over the container to your OpenVZ server or in our case our SolusVM Host box.
rsync -a -e ssh /vz/root/1234 email@example.com:/vz/private/
After that we start the VM on the new host box.
vzctl start 1234
Next you want to console the container
vzctl enter 1234
This will let you test your new Container to make sure it is working correct. If you have a SolusVM server these are the steps you need to take to finish the migration.
1. Add the IP Addresses to SolusVM
2. Add the Client to SolusVM
3. Import the OpenVZ Container into solusvm.
4. Add any extra IP Addresses to SolusVM then to the Container in SolusVM.
5. Go back to Virtuozzo then remove the old IP Addresses and add one new unused IP Address to the Container so Virtuozzo thinks the IP Addresses you moved are not in use.
This is basically how I migrated a whole bunch of Virtuozzo containers to SolusVM.. Like I said this should work for any OpenVZ Server. How ever you could run into issues depending on how OpenVZ is configured. I hope this helps! Good luck with your migration!