On a large cluster, when spinning a large number of VMs (500), not all the VMs are running, and the kubevirt-ipam-controller-manager pod is stuck in a CrashLoopBackOff status.

4.18.0-rc.4

1. On a large cluster, deploy a large amount of VMs (500).

Not all the VMs are running, and the kubevirt-ipam-controller-manager pod is stuck in a CrashLoopBackOff status.
When describing the pod you can see it was terminated due to oomkilled:
    Last State:     Terminated
      Reason:       OOMKilled
      Exit Code:    137

All VMs should be running succesfully.