Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-69378

Changing cluster-level memoryOverCommit requires VM restart to be applied

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • CNV v4.21.0
    • CNV v4.19.2
    • CNV Virt-Node
    • None
    • Quality / Stability / Reliability
    • 8
    • False
    • Hide

      None

      Show
      None
    • False
    • CNV v4.99.0.rhel9-2451, CNV v4.19.16.rhel9-16, CNV v4.21.0.rhel9-24
    • CNV Virt-Node Sprint 277, CNV Virt-Node Sprint 278, CNV Virt-Node Sprint 279, CNV Virt-Node Sprint 280
    • 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.

              jelejosne Jed Lejosne
              fdeutsch@redhat.com Fabian Deutsch
              Denys Shchedrivyi Denys Shchedrivyi
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: