From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
|actions= | |actions= | ||
# Save the F-11 domU using:<pre>$> virsh save f11 /var/lib/xen/save/f11-save</pre> | # Save the F-11 domU using:<pre>$> virsh save f11 /var/lib/xen/save/f11-save</pre> | ||
# Wait 20 to 30 seconds, then run <pre>virsh restore /var/lib/xen/save/f11-save</pre> to restore the guest | # Wait 20 to 30 seconds, then run <pre>$> virsh restore /var/lib/xen/save/f11-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 xen-domu-stress-save-restore.c -o xen-domu-stress-save-restore</pre> | # 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: | # 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 f11 /var/lib/xen/save/f11-save ; virsh restore /var/lib/xen/save/f11-save ; done</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</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= | ||
Revision as of 12:40, 4 May 2009
Description
This test case will verify that a F-11 guest can be saved and restored.
How to test
- Save the F-11 domU using:
$> virsh save f11 /var/lib/xen/save/f11-save
- Wait 20 to 30 seconds, then run
$> virsh restore /var/lib/xen/save/f11-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 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.