On 01/18/2011 05:28 PM, Justin Clift wrote:
This completes the man page updates required for BZ # 622534:
https://bugzilla.redhat.com/show_bug.cgi?id=622534 =item B<setmaxmem> I<domain-id> B<kilobytes>
-Change the maximum memory allocation limit in the guest domain. This should -not change the current memory use. The memory limit is specified in -kilobytes. +Change the maximum memory allocation limit for an active guest domain.
I'm a bit confused here. Doesn't maximum memory allocation only take effect at domain boot? So it seems like something you can't change at runtime, and if a change is made to an active domain, it only affects the configured version and the next boot of the domain rather than having an immediate effect. But I haven't played closely with setmaxmem, so I could be wrong.
+ +Some hypervisors require a larger granularity than kilobytes, and requests +that are not an even multiple will either be rounded down or rejected. For +example, vSphere/ESX rejects the parameter unless the kB argument is evenly +divisible by 1024 (that is, the kB argument happens to represent megabytes). + +Note, this command only works on active guest domains. To change the memory +allocation for an inactive guest domain, use the virsh B<edit> command to +update the XML <memory> element.
I guess this means some experimentation is in order to validate these claims. -- Eric Blake eblake@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org