starting VM with Hugepages configured is causing virt-controller pods to crash
[akriti@fedora vm-yamls]$ oc apply -f vm_with_hugepges.yaml
virtualmachine.kubevirt.io/vm1-rhel-ocs created
[akriti@fedora vm-yamls]$ oc get vm
NAME           AGE   STATUS         READY
vm1-rhel-ocs   10s   Provisioning   False
[akriti@fedora vm-yamls]$ oc get vm
NAME           AGE     STATUS    READY
vm1-rhel-ocs   2m39s   Stopped   False
[akriti@fedora vm-yamls]$ virtctl start vm1-rhel-ocs
VM vm1-rhel-ocs was scheduled to start
[akriti@fedora vm-yamls]$ oc get vm
NAME           AGE     STATUS    READY
vm1-rhel-ocs   2m52s   Stopped   False
[akriti@fedora vm-yamls]$ oc get pods -A | grep -v Running
NAMESPACE                                          NAME                                                                            READY   STATUS             RESTARTS         AGE
openshift-cnv                                      virt-controller-695fc5f58d-b6cs6                                                0/1     CrashLoopBackOff   11 (4m17s ago)   95m
openshift-cnv                                      virt-controller-695fc5f58d-wzn4j                                                0/1     CrashLoopBackOff   11 (4m33s ago)   95m

1.create a vm with Hugepages configured
2.start the vm 
3.monitor virt-controller pods

pods are in CrashLoopBackOff state

pods are running fine and vm starts

this is also impacting starting other VMs on the cluster