Created attachment 1168762 [details]
Screenshot from 2016-06-16 18:03:57.png

there are 2 issues here:
1: it is indeed presented visually incorrectly
2: the minAllocatedMem can be applied also immediately and does not require VM restart, so should be handled similarly than the memory (e.g. the user can choose to apply immediately or later)

This bug had requires_doc_text flag, yet no documentation text was provided. Please add the documentation text and only then set this flag.

any issue with applying minAllocatedMem immediately when editing running VM?

I believe the engine is not sending the value to VDSM when the VM is already running. Otherwise there would be no issue, MOM would read the new value from VDSM and act accordingly.

adding a parameter to the hotplug call should be fairly simple

Originally the bug report misleading text in the dialog.
the dialog display:
"minAllocatedMem" as field that is require restart. 

Changing the min alocation memory reuqire updating vdsm and engine sla.
There is no need for that now, will apply the text change only.

oVirt 4.1.0 GA has been released, re-targeting to 4.1.1.
Please check if this issue is correctly targeted or already included in 4.1.0.

The change in 4.1.0 is not yet included, seen it on Red Hat Virtualization Manager Version: 4.1.0.3-0.1.el7.
When trying to change RAM for running guest VMs, message appears as follows:

"Pending Virtual Machine changes
Changes that can be applied immediately:

    Memory

Apply later
Changes that require Virtual Machine restart:

    maxMemorySizeMb

    minAllocatedMem
"

Tested on host:
rhvm-appliance-4.1.20170126.0-1.el7ev.noarch
sanlock-3.4.0-1.el7.x86_64
ovirt-node-ng-nodectl-4.1.0-0.20170104.1.el7.noarch
qemu-kvm-rhev-2.6.0-28.el7_3.3.x86_64
vdsm-4.19.4-1.el7ev.x86_64
ovirt-imageio-common-1.0.0-0.el7ev.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch
ovirt-setup-lib-1.1.0-1.el7ev.noarch
ovirt-vmconsole-host-1.0.4-1.el7ev.noarch
mom-0.5.8-1.el7ev.noarch
ovirt-imageio-daemon-1.0.0-0.el7ev.noarch
ovirt-hosted-engine-ha-2.1.0.1-1.el7ev.noarch
ovirt-hosted-engine-setup-2.1.0.1-1.el7ev.noarch
ovirt-vmconsole-1.0.4-1.el7ev.noarch
libvirt-client-2.0.0-10.el7_3.4.x86_64
ovirt-host-deploy-1.6.0-1.el7ev.noarch
Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016
Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 7.3

Engine:
rhevm-setup-plugins-4.1.0-1.el7ev.noarch
rhevm-dependencies-4.1.0-1.el7ev.noarch
rhevm-doc-4.1.0-2.el7ev.noarch
rhev-guest-tools-iso-4.1-3.el7ev.noarch
rhevm-4.1.0.3-0.1.el7.noarch
rhevm-branding-rhev-4.1.0-0.el7ev.noarch
Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016
Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.3 (Maipo)

it suppose to make it to 4.1.1

Moving to verified forth to this bug now fixed and message being shown as appears bellow:	
	
Pending Virtual Machine changes
Changes that can be applied immediately:

    Memory

Apply later
Changes that require Virtual Machine restart:

    Maximum Memory

    Physical Memory Guaranteed

Engine's components:
rhevm-setup-plugins-4.1.0-1.el7ev.noarch
rhevm-dependencies-4.1.0-1.el7ev.noarch
rhevm-doc-4.1.0-2.el7ev.noarch
rhev-guest-tools-iso-4.1-3.el7ev.noarch
rhevm-4.1.1-0.1.el7.noarch
rhevm-branding-rhev-4.1.0-0.el7ev.noarch
Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016
Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.3 (Maipo)

Created attachment 1250527 [details]
Screenshot from 2017-02-15 10-55-20.png