From Fedora Project Wiki
No edit summary |
(add {{autolang}}) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{autolang|base=yes}} | |||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test case will verify that a | |description=This test case will verify that a rawhide guest can be saved and restored. | ||
|actions= | |actions= | ||
# Save the | # Save the rawhide domU using:<pre>$> virsh save rawhide /var/lib/xen/save/rawhide-save</pre> | ||
# Wait 20 to 30 seconds, then run <pre>$> virsh restore /var/lib/xen/save/ | # Wait 20 to 30 seconds, then run <pre>$> virsh restore /var/lib/xen/save/rawhide-save</pre> to restore the guest | ||
# 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. | ||
# Copy [[File:Xen-domu-stress-save-restore.c]] into the guest, then compile it with <pre>$> gcc -O2 | # Copy [[File:Xen-domu-stress-save-restore.c]] into the guest, then compile it with <pre>$> gcc -O2 Xen-domu-stress-save-restore.c -o Xen-domu-stress-save-restore</pre> | ||
# Now run the resulting executable inside the guest <pre>$> ./xen-domu-stress-save-restore</pre> | # Now run the resulting executable inside the guest <pre>$> ./xen-domu-stress-save-restore</pre> | ||
# While the test is running in the guest, run a few save/restore iterations in the dom0:<pre>$> for i in `seq 1 10` ; do virsh save | # While the test is running in the guest, run a few save/restore iterations in the dom0:<pre>$> for i in `seq 1 10` ; do virsh save rawhide /var/lib/xen/save/rawhide-save ; virsh restore /var/lib/xen/save/rawhide-save ; done</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= | ||
Latest revision as of 09:42, 13 April 2011
Description
This test case will verify that a rawhide guest can be saved and restored.
How to test
- Save the rawhide domU using:
$> virsh save rawhide /var/lib/xen/save/rawhide-save
- Wait 20 to 30 seconds, then run
$> virsh restore /var/lib/xen/save/rawhide-save
to restore the guest - 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, then compile it with
$> gcc -O2 Xen-domu-stress-save-restore.c -o Xen-domu-stress-save-restore
- Now run the resulting executable inside the guest
$> ./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 rawhide /var/lib/xen/save/rawhide-save ; virsh restore /var/lib/xen/save/rawhide-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.