On 03/05/09 12:27, John Levon wrote:
mem-set affects the running guest (balloon driver), but mem-max does not
(it will only apply after a reboot). All kernels use the max-mem value
for precisely what you suggest, and they won't see any changes in the
value until they're rebooted (that is, no memory hotplug, only balloon).
Ok, so maybe I am being foolish in even trying to support a dynamic
change to mem-max (memory hotplug) in my kernel. I notice there is no
equivalent of "target" (mem-set) to watch for a change, so I actually
check mem-max whenever I get a mem-set event.
I don't understand how kernels see the change after a reboot, unless
this is related to managed domains and the xm mem-max setting is being
squirreled away for the next time the guest runs.
Mick
_______________________________________________
xen-discuss mailing list
[email protected]
