From Fedora Project Wiki

(add sort key)
Line 4: Line 4:
 
* To save and restore the guest, run:
 
* To save and restore the guest, run:
 
<pre>
 
<pre>
   $> xm save f11 /var/lib/xen/save/f11-save
+
   $> virsh save f11 /var/lib/xen/save/f11-save
 
   $> sleep 20
 
   $> sleep 20
   $> xm restore /var/lib/xen/save/f11-save
+
   $> virsh restore /var/lib/xen/save/f11-save
 
</pre>
 
</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.
Line 12: Line 12:
 
* Copy [[File:Xen-domu-stress-save-restore.c|foo]] into the guest, compile and run with:
 
* Copy [[File:Xen-domu-stress-save-restore.c|foo]] into the guest, compile and run with:
 
<pre>
 
<pre>
$> gcc -O0 -Wall -g xen-domu-stress-save-restore.c -o xen-domu-stress-save-restore
+
$> gcc -O2 xen-domu-stress-save-restore.c -o xen-domu-stress-save-restore
 
$> ./xen-domu-stress-save-restore
 
$> ./xen-domu-stress-save-restore
 
</pre>
 
</pre>
 
* While the test is running in the guest, run a few save/restore iterations in the dom0:
 
* While the test is running in the guest, run a few save/restore iterations in the dom0:
 
<pre>
 
<pre>
$> for i in `seq 1 10` ; do xm save f11 /var/lib/xen/save/f11-save ; xm restore /var/lib/xen/save/f11-save ; done
+
$> 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
 
</pre>
 
</pre>
 
* 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.
 
* 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.
 
|results=
 
|results=
* The save/restores complete successfully with now oops, lockups or error messages.
+
* The save/restores complete successfully with no oops, lockups or error messages.
 
}}
 
}}
 
[[Category:Virtualization XenDomU Test Cases|Save and restore]]
 
[[Category:Virtualization XenDomU Test Cases|Save and restore]]

Revision as of 09:05, 4 May 2009

Description

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


How to test

  • To save and restore the guest, run:
  $> virsh save f11 /var/lib/xen/save/f11-save
  $> sleep 20
  $> virsh restore /var/lib/xen/save/f11-save
  • 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.
  • 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
  • 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
  • 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

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