From: Peter Krempa <pkrempa@redhat.com>
Date: Fri, 22 Mar 2013 10:05:36 +0000 (+0100)
Subject: virsh: Fix docs for "virsh setmaxmem"
X-Git-Tag: v1.0.4-rc1~7
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b88831f75185bb5d9e1a8f389a3af0892990f072;p=thirdparty%2Flibvirt.git

virsh: Fix docs for "virsh setmaxmem"

The docs assumed the command works always for QEMU and other
hypervisors. As this is done using the balloon mechainism live increase
of the maximum memory limit isn't supported. Fix the docs to mention
this limitation.
---

diff --git a/tools/virsh.pod b/tools/virsh.pod
index b5e632e9ea..07e7c24aba 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -1477,7 +1477,8 @@ Both I<--live> and I<--config> flags may be given, but I<--current> is
 exclusive. If no flag is specified, behavior is different depending
 on hypervisor.
 
-This command works for at least the Xen, QEMU/KVM and vSphere/ESX hypervisors.
+Some hypervisors such as QEMU/KVM don't support live changes (especially
+increasing) of the maximum memory limit.
 
 I<size> is a scaled integer (see B<NOTES> above); it defaults to kibibytes
 (blocks of 1024 bytes) unless you provide a suffix (and the older option