Live migration project
The purpose of this project was to be able to move a virtual server from one system to another system with out having to shut it down.
Setup three server
Frosty.student.lab, ip 10.80.3.230 xen server and nfs client
Purple.student.lab, ip 10.80.3.231 xen server and nfs client
Mellow.student.lab ip 10.80.3.232 NFS server and holder of the afs virtual disk
Step 1 Using procedure Vertual Server Install to build two virtual xen server. (Frosty and Purple)
Step 2. Build a third server Desk Top Install do not install gnome. (Mellow)
Step 3 Install nfs on Mellow using procedure nfs_install
Step 4 Create the virtual disk for the afs partition the process for the can be found in the first section of the afs_install procedure afs_install
Step 5. I then logged on to vmserver02 and did the following
cd /xen
scp conf/vm14.cfg root@10.80.3.230:/xen
scp conf/vm15.cfg root.@10.80.3.230:/xen
scp conf/vm16.cfg root.@10.80.3.230:/xen
This copied vm14 vm15 and vm16 to the nfs space on 10.80.3.232
Step 6.Login to 10.80.3.230 (Frosty.student.lab) and following the section called launching your VM outline in http://lab46.corning-cc.edu/haas/hpc0/projects/creating_virtual_machines
do a xm create -c /xen/conf/vm14.cfg
once the vm is booted using a ctrl-] to detach
repeat the process, this time starting vm15
xm create -c /xen/conf/vm15.cfg
ctrl-]
Step 7. Login to 10.80.3.231(Purple.student.lab) repeat the process used for starting vm14 and 15 only we will be starting vm16
xm create -c /xen/conf/vm16.cfg
ctrl-]
At this point the afs cell should be up and running as if it was still on vmserver02.student.lab.
The next step test the ojective of the whole project.
Step 8. Login to 10.80.3.230(Mellow), this is the system we will migrate vm16 to from 10.80.3.231(Purple)
xm migrate –live vm16 Purple
If you want to verify that this is a live magration you could have open another terminal window and started a ping of vm16.student.lab and saw the there was only a small lag in packets as the switch occurred. Not long enough that any user logged on to vm16 would have noticed it.