From b88831f75185bb5d9e1a8f389a3af0892990f072 Mon Sep 17 00:00:00 2001 From: Peter Krempa Date: Fri, 22 Mar 2013 11:05:36 +0100 Subject: [PATCH] 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. --- tools/virsh.pod | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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 is a scaled integer (see B above); it defaults to kibibytes (blocks of 1024 bytes) unless you provide a suffix (and the older option -- GitLab