Revision as of 15:40, 15 September 2009

Description

This test case checks that a Fedora Xen DomU can balloon to various memory sizes.

Use $> free -m to check the memory available to the guest.
Shutdown the guest and edit your xen configuration file (e.g. in /etc/xen). Either add or modify the "maxmem" parameter in that file, adjusting it to the amount of memory you have in your machine minus 1GB (to save for the dom0). For example, if you have a machine with 4GB of memory, then set the maxmem parameter to 3000.
Start guest again. Check that the same amount of memory is available as before, again using $> free -m.
Balloon down the Dom0. On the command-line of the Dom0, as root run
```
$> virsh setmem Domain-0 $(( 900 * 1024 ))
```
Check that Dom0 now only has 900Mb available.
Still on the Dom0 command-line, balloon up the guest using
```
$> virsh setmem rawhide $(( 3000 * 1024 ))
```
Wait about 20 seconds and use $> free -m inside the guest to check that the guest now has the specified amount of memory available.
Repeat the last step for a number of different values. Especially if you have a machine with > 4GB of memory, repeatedly balloon the guest above and below the 4GB boundary, try other values, etc.

Guest should not crash while ballooning up and down, no matter what values are given.
Guest should not have any softlockup or other warning messages in dmesg while ballooning up and down.

@@ Line 1: / Line 1: @@
 {{QA/Test_Case
-|description=This test case checks that a Rawhide Xen DomU can balloon to various memory sizes.
+|description=This test case checks that a Fedora Xen DomU can balloon to various memory sizes.
 |actions=
 # Use <code>$> free -m</code> to check the memory available to the guest.