Possible workaround in https://kubevirt.io/monitoring/runbooks/KubeVirtComponentExceedsRequestedMemory.html ?

*** Bug 2166385 has been marked as a duplicate of this bug. ***

Note:
1) Directly patching KubeVirt CR would get reconciled and reset to the original default values
2) We need to patch KubeVirt CR only via HCO CR, using the below command.

If needed, the command to patch virt-controller Deployment and increase the memory is, 

oc annotate --overwrite -n openshift-cnv hyperconverged kubevirt-hyperconverged \
  kubevirt.kubevirt.io/jsonpatch='[
    {
      "op": "add",
      "path": "/spec/customizeComponents/patches",
      "value": [{
          "patch": "[{\"op\":\"add\",\"path\":\"/spec/template/spec/containers/0/resources/requests\",\"value\":{\"cpu\": \"10m\",\"memory\": \"400Mi\"}}]",
          "resourceName": "virt-controller",
          "resourceType": "Deployment",
          "type": "json"
      }]
    }
  ]'

Note: We updating memory to be 400Mi here, just as an example, this does not mean that, these are the recommended values.

The above command would add annotations to HCO CR,

]$ oc get hyperconverged kubevirt-hyperconverged -n openshift-cnv -o yaml 
apiVersion: hco.kubevirt.io/v1beta1
kind: HyperConverged
metadata:
  annotations:
    kubevirt.kubevirt.io/jsonpatch: |-
      [
          {
            "op": "add",
            "path": "/spec/customizeComponents/patches",
            "value": [{
                "patch": "[{\"op\":\"add\",\"path\":\"/spec/template/spec/containers/0/resources/requests\",\"value\":{\"cpu\": \"10m\",\"memory\": \"400Mi\"}}]",
                "resourceName": "virt-controller",
                "resourceType": "Deployment",
                "type": "json"
            }]
          }
        ]

verify with build: CNV-v4.10.9-53

test all virt components, requested memory is greater than the used memory, move to verified.

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 (OpenShift Virtualization 4.10.9 RPMs), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:3573