From Fedora Project Wiki

Line 2: Line 2:
 
|description=This test case will verify that a F-11 guest can be saved and restored.
 
|description=This test case will verify that a F-11 guest can be saved and restored.
 
|actions=
 
|actions=
# To save and restore the guest, run:
+
# Save the F-11 domU using:<pre>$> virsh save f11 /var/lib/xen/save/f11-save</pre>
<pre>
+
# Wait 20 to 30 seconds, then run <pre>virsh restore /var/lib/xen/save/f11-save</pre> to restore the guest
  $> virsh save f11 /var/lib/xen/save/f11-save
 
  $> sleep 20
 
  $> virsh restore /var/lib/xen/save/f11-save
 
</pre>
 
 
# After the guest is restored, make sure it has the right memory size, the right number of processors, no softlockups, etc.
 
# After the guest is restored, make sure it has the right memory size, the right number of processors, no softlockups, etc.
 
# Run the previous step with varying memory sizes for the guest, notably around the 4GB boundary.
 
# Run the previous step with varying memory sizes for the guest, notably around the 4GB boundary.

Revision as of 12:38, 4 May 2009

Description

This test case will verify that a F-11 guest can be saved and restored.


How to test

  1. Save the F-11 domU using:
    $> virsh save f11 /var/lib/xen/save/f11-save
  2. Wait 20 to 30 seconds, then run
    virsh restore /var/lib/xen/save/f11-save
    to restore the guest
  3. After the guest is restored, make sure it has the right memory size, the right number of processors, no softlockups, etc.
  4. Run the previous step with varying memory sizes for the guest, notably around the 4GB boundary.
  5. Copy File:Xen-domu-stress-save-restore.c into the guest, compile and run with:
$> gcc -O2 xen-domu-stress-save-restore.c -o xen-domu-stress-save-restore
$> ./xen-domu-stress-save-restore
  1. While the test is running in the guest, run a few save/restore iterations in the dom0:
$> for i in `seq 1 10` ; do virsh save f11 /var/lib/xen/save/f11-save ; virsh restore /var/lib/xen/save/f11-save ; done
  1. Similarly, put the guest under some load - e.g. a kernel compile or program that allocates and modifies large amounts of memory - and run many save/restore iterations.

Expected Results

  1. The save/restores complete successfully with no oops, lockups or error messages.