From Fedora Project Wiki
No edit summary |
No edit summary |
||
| 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: | |||
<pre> | <pre> | ||
$> virsh save f11 /var/lib/xen/save/f11-save | $> virsh save f11 /var/lib/xen/save/f11-save | ||
| Line 8: | Line 8: | ||
$> virsh 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. | |||
# Run the previous step with varying memory sizes for the guest, notably around the 4GB boundary. | |||
# Copy [[File:Xen-domu-stress-save-restore.c|foo]] into the guest, compile and run with: | |||
<pre> | <pre> | ||
$> gcc -O2 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: | |||
<pre> | <pre> | ||
$> 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 | $> 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. | |||
|results= | |results= | ||
# 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 12:35, 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.