QA:Testcase Live Migration using libvirt/virsh

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Completely rework the page, add lot's of preparation steps, use modern test case format)
Line 1: Line 1:
{{autolang|base=yes}}
+
 
  
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case checks that basic live migration using libvirt between two Fedora hosts works correctly.
+
|description=
 +
Live migrate a VM between 2 Fedora hosts, and verify it is running correctly on the new host. These test steps aim for the simplest setup possible, using just a single host and two VMs: one as the migration destination, and one VM to migrate.
 +
 
 +
|setup=
 +
 
 +
If you've been following along with a test day, you should have an up to date Fedora VM available. This will be the host that we migrate the VM to.
 +
 
 +
{{ admon/warning | The default network setup does not allow the migrated guest to maintain continuous network connectivity. | In real deployments you would want to use bridged networking, but it isn't required for these basic tests. }}
 +
 
 +
== SSH key access ==
 +
 
 +
* On the physical host, create an SSH key for root:
 +
** <code>su -</code>
 +
** <code>ssh-keygen</code>
 +
 
 +
* Set up the SSH key as an authorized key for the destination host VM
 +
** <code>sudo virsh start test-day-vm</code>
 +
** <code>virt-viewer --connect qemu:///system test-day-vm</code>
 +
** Open a terminal, <code>su -</code>
 +
** <code>mkdir -p /root/.ssh && chmod 700 /root/.ssh</code>
 +
 
 +
== Create the VM to migrate ==
 +
 
 +
If you've been following the test day, you likely only have 1 VM created. Feel free to skip this step if you have multiple VMs available.
 +
 
 +
* Clone the existing test day VM: <code>sudo virt-clone -o test-day-vm -n test-day-vm-migrate --auto-clone</code>
 +
* If your test day VM is using nested virt, you want to turn that off for the new VM since it can cause migration compatibility issues since we are migrating into a VM:
 +
** <code>sudo virsh edit test-day-vm-migrate</code>
 +
** Delete the entire <cpu> block
 +
* Edit the guest so that it has a smaller amount of memory. My destination had 4G, and the migrating VM had 2G. You can likely much smaller.
 +
* Start the VM, verify it works correctly.
 +
 
 +
== Sharing storage ==
 +
 
 +
Inside the destination VM, setup shared storage using sshfs:
 +
 
 +
* <code>sudo virsh start test-day-vm && virt-viewer --connect qemu:///system test-day-vm</code>
 +
* <code>yum install sshfs</code>
 +
* <code>sshfs root@HOST-IP:/var/lib/libvirt/images /var/lib/libvirt/images</code>
 +
* <code>sudo setsebool -P virt_use_fusefs=1</code>
 +
* Edit /etc/libvirt/qemu.conf, uncomment user=root and group=root, <code>sudo service libvirtd restart</code>
 +
** XXX: That part is likely a bug
 +
 
 +
 
 
|actions=
 
|actions=
# On the source machine, edit the guest so that it has some small amount of memory (say, 768MB).
+
 
# On the source machine, start the guest.
+
# On the source host, prep the migration:
# Once the guest has fully booted, find out the IP address of the guest (by logging into the guest and running ifconfig, or whatever is equivalent in the guest OS of your choice). From the source machine, start a ping to the guest:<br><br><code>$ ping <guest-IP></code><br><br>
+
#* <code>source-host$ sudo virsh start test-day-vm-migrate< && virt-viewer --connect qemu:///system test-day-vm-migrate/code>
# Now on the source machine execute:<br><br><code>$ virsh migrate --live <guestname> qemu+ssh://<destination host>/system</code><br><br>
+
#* Log in to the guest graphical desktop. Open a terminal, start a simple loop like <code>dest-vm$ for i in `seq 1 10000`; do echo $i; sleep 1; done
# Shutdown the guest on the destination machine.  Once it's successfully shut down, edit the guest on the source machine and give it random, differing amounts of memory: 1024MB, 2111MB, etc.  Then repeat the test for these differing amounts of memory.
+
# The destination host VM should be started and have storage prepped as mentioned above.
# Repeat the entire test for as many different guest OS's as are relevant.  We would at least like to see the following guests:
+
# On the source host, perform the migration: <code>source-host$ sudo virsh migrate --verbose --live --p2p --tunnelled test-day-vm-migrate
## Fedora 16
+
# After migration completes, verify the migrated VM is running on the destination
## Fedora 15
+
#* <code>source-host$ virt-viewer --connect qemu:///system test-day-vm</code>
## RHEL-5
+
#* <code>dest-vm$ virt-viewer --connect qemu:///system test-day-vm-migrate</code>
## RHEL-6
+
#* Verify the simple echo loop is still running, guest appears to be working okay.
## Windows XP
+
# Stop the migrated VM:
## Windows Vista
+
#* <code>dest-vm$ sudo virsh destroy test-day-vm-migrate</code>
## SUSE
+
#* Verify that after destroying the VM, it no longer appears in <code>dest-vm$ sudo virsh list --all</code> . (that is because we didn't pass the --persistent option to 'virsh migrate')
 +
# Verify that the VM is stopped on the original host: <code>source-host$ sudo virsh list --all</code>  (the VM is still there because we didn't pass the --undefinesource option to 'virsh migrate')
 +
 
 +
 
 
|results=
 
|results=
# After executing the virsh migrate command, the guest should migrate over to the destination machine, and not be running anymore on the source machine. Use <code>$ virsh list</code> on both machines to verify this.  Additionally, the ping that was started in step 3 should continue uninterrupted.
+
All steps complete without error and the migrated VM behaves as expected.
 +
 
 +
# Step #1 completes without error
 +
# The system boots into runlevel 5
 +
# Program completes with exit code 0
 +
 
 +
|optional=
 +
If you have pre-existing VMs of other operating systems, please try migrating those as well.
 
}}
 
}}
[[Category:Virtualization Live Migration]]
+
 
 +
[[Category:Virtualization Test Cases]]

Revision as of 12:47, 24 May 2013


Contents

Description

Live migrate a VM between 2 Fedora hosts, and verify it is running correctly on the new host. These test steps aim for the simplest setup possible, using just a single host and two VMs: one as the migration destination, and one VM to migrate.

Setup

If you've been following along with a test day, you should have an up to date Fedora VM available. This will be the host that we migrate the VM to.

Warning (medium size).png
The default network setup does not allow the migrated guest to maintain continuous network connectivity.
In real deployments you would want to use bridged networking, but it isn't required for these basic tests.

SSH key access

  • On the physical host, create an SSH key for root:
    • su -
    • ssh-keygen
  • Set up the SSH key as an authorized key for the destination host VM
    • sudo virsh start test-day-vm
    • virt-viewer --connect qemu:///system test-day-vm
    • Open a terminal, su -
    • mkdir -p /root/.ssh && chmod 700 /root/.ssh

Create the VM to migrate

If you've been following the test day, you likely only have 1 VM created. Feel free to skip this step if you have multiple VMs available.

  • Clone the existing test day VM: sudo virt-clone -o test-day-vm -n test-day-vm-migrate --auto-clone
  • If your test day VM is using nested virt, you want to turn that off for the new VM since it can cause migration compatibility issues since we are migrating into a VM:
    • sudo virsh edit test-day-vm-migrate
    • Delete the entire <cpu> block
  • Edit the guest so that it has a smaller amount of memory. My destination had 4G, and the migrating VM had 2G. You can likely much smaller.
  • Start the VM, verify it works correctly.

Sharing storage

Inside the destination VM, setup shared storage using sshfs:

  • sudo virsh start test-day-vm && virt-viewer --connect qemu:///system test-day-vm
  • yum install sshfs
  • sshfs root@HOST-IP:/var/lib/libvirt/images /var/lib/libvirt/images
  • sudo setsebool -P virt_use_fusefs=1
  • Edit /etc/libvirt/qemu.conf, uncomment user=root and group=root, sudo service libvirtd restart
    • XXX: That part is likely a bug

How to test

  1. On the source host, prep the migration:
    • source-host$ sudo virsh start test-day-vm-migrate< && virt-viewer --connect qemu:///system test-day-vm-migrate/code>
    • Log in to the guest graphical desktop. Open a terminal, start a simple loop like <code>dest-vm$ for i in `seq 1 10000`; do echo $i; sleep 1; done
  2. The destination host VM should be started and have storage prepped as mentioned above.
  3. On the source host, perform the migration: <code>source-host$ sudo virsh migrate --verbose --live --p2p --tunnelled test-day-vm-migrate
  4. After migration completes, verify the migrated VM is running on the destination
    • <code>source-host$ virt-viewer --connect qemu:///system test-day-vm
    • dest-vm$ virt-viewer --connect qemu:///system test-day-vm-migrate
    • Verify the simple echo loop is still running, guest appears to be working okay.
  5. Stop the migrated VM:
    • dest-vm$ sudo virsh destroy test-day-vm-migrate
    • Verify that after destroying the VM, it no longer appears in dest-vm$ sudo virsh list --all . (that is because we didn't pass the --persistent option to 'virsh migrate')
  6. Verify that the VM is stopped on the original host: source-host$ sudo virsh list --all (the VM is still there because we didn't pass the --undefinesource option to 'virsh migrate')

Expected Results

All steps complete without error and the migrated VM behaves as expected.

  1. Step #1 completes without error
  2. The system boots into runlevel 5
  3. Program completes with exit code 0

Optional

If you have pre-existing VMs of other operating systems, please try migrating those as well.