Webramz blog

Few months after HyperVM developer found dead, It was so sad, and I think HyperVM has a long road to go, specially when I saw the source of hypervm published, I looked at it and though, it is not a code which you can rely on.

Hypervm was programmed in plain inline code without any code design pattern in behind. But to be honest, it performed a great role to change vps businesses around the world.

So I though, we have to move to a new vps management system, and finally picked SolusVM. Have to say it was a great choice, and in last two months, it did good job, these guys are promising.

Solus Virtual Manager (SolusVM) is a powerful GUI based VPS management system with full OpenVZ and Xen support with KVM to be released shortly. SolusVM allows you and your clients to manage a VPS cluster with security & ease.

You may faced situation when you hang to do a simple job. Yes, there are most of times, simple answers to resolve issues, but not mentioned anywhere. One of those is when you want to migrate a vps from one node to another with hypervm. You are lucky if you do this without getting any error, and if so, why do you reached this post?

After 6 hours of hammering my head, I got it to work and I post this here to help you and others.

Before starting migration, you MUST do steps below if you want to success:

1. Make sure partition of /usr/local/lxlabs/hypervm/serverfile/tmp on source HN have enough space to dump vps into, or just remove it and create a symlink to another folder/partiotion which have enough space.

2. Make sure /tmp partition on destination HN have enough space, if not you can mount –bind it to another folder in another partition. (only if /tmp is partition, if not just create symlinks) for more info see: http://www.ibm.com/developerworks/library/l-fs3.html

3. Disable firewalls on both HN, so they do not block each other packets (simply disable/enable firewalls, openning ports does not give you the results always.)

4. Ssh to dest HN, from source HN, and make sure you can login without prompt of password. (Using public keys)

5. Now run

cd /usr/local/lxlabs/hypervm/httpdocs;

/usr/local/lxlabs/ext/php/php ../bin/common/switchserver.php ––priority=low ––class=vps ––name=VPS_NAME.vm ––v-syncserver=DEST_HN_IP

(change VPS_NAME and DEST_HN_IP with proper values)
6. check logs with command tail -f /usr/local/lxlabs/hypervm/log/shell_exec on both servers, and find any errors.

Take a cup of coffe and relax, I hope

After migration, you must change IP of new vps throught hypervm and cPanel/Plesk/DirectAdmin…