Description of problem: Up to RHEV 3.2, KSM was controlled by ksmtuned. Users wanting stop KSM just wanted to stop ksmtuned service. In RHEV 3.3, vdsm stops ksmtuned and gives KSM control to MOM. MOM controls KSM and memory ballooning. We can disable memory ballooning using RHEV Admin Portal interface, unchecking "Enable Memory Balloon Optimization" in Cluster level, which will have effect in next Host "Up", or using emergencial vdsClient on the Hypervisor: # vdsClient -s 0 setMOMPolicyParameters balloonEnabled=False Please provide an equivalent way to disable KSM in RHEV 3.3.
can you provide any information how to test this?
vdsClient -s 0 setMOMPolicyParameters ksmEnabled=False This command should disable KSM. You can then use MoM's xml-rpc, call getPolicy() and check if the ksmEnabled variable is indeed set to False. There will be two parts - (defvar ksmEnabled True) as a default and (set ksmEnabled False) representing the updated value.
Also please make sure that the value is still there when you subsequently call setMOMPolicyParameters with only balloonEnabled=False. In other words: vdsClient -s 0 setMOMPolicyParameters ksmEnabled=False vdsClient -s 0 setMOMPolicyParameters balloonEnabled=False should give you the same result as vdsClient -s 0 setMOMPolicyParameters ksmEnabled=False balloonEnabled=False
thanks Martin, tested in is28 moving to VERIFIED
*is27, sorry typo
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0040.html