Ben Thomas
2006-Oct-31 19:42 UTC
[Xen-devel] [PATCH] add dom0_max_mem hypervisor boot option
If you want to set dom0 to a specific memory size on a specific
machine, you can use the hypervisor boot option, dom0_mem. However,
when working with a number of nodes, you may simply want to cap
dom0 memory usage without regard to the specific amount of memory
on each node. FOr this case, you cannot use dom0_mem, as the node
must have that much memory or more. For this case, the boot option
dom0_max_mem was added. If dom0_mem is unspecified (to preserve
current behavior), it will act as a ceiling/cap on the amount of
memory available to construct dom0. Nodes with less memory will
continue to use all of their memory; nodes with more will apply
only the specified portion to dom0. Many words - simple idea.
Simple example: dom0 on all nodes should be 2GB or less, use the
option dom0_max_mem=2G
Signed-off-by: Ben Thomas (ben@virtualiron.com)
--
------------------------------------------------------------------------
Ben Thomas Virtual Iron Software
bthomas@virtualiron.com Tower 1, Floor 2
978-849-1214 900 Chelmsford Street
Lowell, MA 01851
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel