setmaxmem: remove the code to invoke virDomainSetMemory in cmdSetmaxmem

When the new maximum memory size becomes less than the current memory size,
I think it is not the libvirt client but the each driver that decides the behavior
(reject the operation or shrink the current memory size).

Signed-off-by: Taku Izumi <izumi.taku@jp.fujitsu.com>

diff --git a/tools/virsh.c b/tools/virsh.c
index f2d2c9d1a5ad03d282d43eba903cd2e4025f72a9..a718abf09d2d739701e68ba1f5e8b138e0a7a6b6 100644 (file)
--- a/tools/virsh.c
+++ b/tools/virsh.c
@@ -3046,15 +3046,7 @@ cmdSetmaxmem(vshControl *ctl, const vshCmd *cmd)
 
     if (virDomainSetMaxMemory(dom, kilobytes) != 0) {
         vshError(ctl, "%s", _("Unable to change MaxMemorySize"));
-        virDomainFree(dom);
-        return FALSE;
-    }
-
-    if (kilobytes < info.memory) {
-        if (virDomainSetMemory(dom, kilobytes) != 0) {
-            vshError(ctl, "%s", _("Unable to shrink current MemorySize"));
-            ret = FALSE;
-        }
+        ret = FALSE;
     }
 
     virDomainFree(dom);