-
Bug
-
Resolution: Unresolved
-
Major
-
CNV v4.19.2
-
None
-
Quality / Stability / Reliability
-
8
-
False
-
-
False
-
CNV v4.19.11.rhel9-13
-
-
CNV Virt-Node Sprint 277, CNV Virt-Node Sprint 278
-
None
Description of problem:
Changing cluster level memoryOverCommit requires VM restart to be applied
Version-Release number of selected component (if applicable):
4.19
How reproducible:
Always
Steps to Reproduce:
1. Create a VM 2. Change kubevirt CR memoryOverCommit 3. Check the VM memory overcommit ratio 4. Live migrate the vm 5. Check the VM memory overcommit ratio
Actual results:
At step 3 the overcommit ratio is not applied At step 5 the overcommit ratio is not applied
Expected results:
overcommit ratio is getting applied after step4, thus is adjusted in step 5
Additional info:
live migration should lead to the memoryOvercommit to get into effect in order to avoid that VMs have to be interrupted.
