Addresses BZ # 622534: https://bugzilla.redhat.com/show_bug.cgi?id=622534 --- tools/virsh.pod | 17 ++++++++++++++--- 1 files changed, 14 insertions(+), 3 deletions(-) diff --git a/tools/virsh.pod b/tools/virsh.pod index 4e8b295..0d37512 100644 --- a/tools/virsh.pod +++ b/tools/virsh.pod @@ -584,9 +584,20 @@ update the XML <currentMemory> element. =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 inactive guest domain. + +This command works for at least the Xen and vSphere/ESX hypervisors, +but not for QEMU/KVM. + +Some hypervisors require a larger granularity than kilobytes, rounding down +or rejecting requests that are not an even multiple of the desired amount. +vSphere/ESX is one of these, requiring the parameter to be evenly divisible +by 4MB. For example with vSphere/ESX, 262144 (256MB) is valid as it's a +multiple of 4MB; 263168 (257MB) is not valid as it's not a multiple of 4MB; +266240 (260MB) is also valid, as it's a multiple of 4MB. + +Note, to change the maximum memory allocation for a QEMU/KVM guest domain, +use the virsh B<edit> command instead to update its XML <memory> element. =item B<memtune> I<domain-id> optional I<--hard-limit> B<kilobytes> optional I<--soft-limit> B<kilobytes> optional I<--swap-hard-limit> -- 1.7.3.5