Description of problem:
[rhel9-cnv] VM fails to start with message: Couldn't configure ip nat rules

Version-Release number of selected component (if applicable):
v4.10.0-7 ( RHEL9) / registry-proxy.engineering.redhat.com/rh-osbs/iib:168613

How reproducible:
Create and start a VM using RHEL-9 CNV Builds

Steps to Reproduce:
1. Create either a  DV or cDisk Based VM
2. 
3.

Actual results:
DV based VM
------------
{"component":"virt-handler","level":"error","msg":"virt-launcher crashed due to a network error. Updating VMI vm-rhel84-ocs status to Failed","pos":"vm.go:1120","timestamp":"2022-02-08T16:45:41.058355Z"}
{"component":"virt-handler","level":"error","msg":"failed to create ipv4 nat rules for vm error: Couldn't configure ip nat rules","pos":"masquerade.go:127","reason":"Couldn't configure ip nat rules","timestamp":"2022-02-08T16:49:51.024375Z"}

containerDisk based VM
-----------------------
{"component":"virt-handler","level":"error","msg":"failed to prepare pod networking","pos":"podnic.go:223","reason":"Couldn't configure ip nat rules","timestamp":"2022-02-08T16:49:51.024436Z"}
{"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"vm2-rhel84","namespace":"default","pos":"vm.go:1685","reason":"failed to configure vmi network: setup failed, err: failed plugging phase1 at nic 'eth0': Critical network error: Couldn't configure ip nat rules","timestamp":"2022-02-08T16:49:51.024532Z","uid":"8af0f412-008d-4975-af08-8abf116a8b76"}


Expected results:
VM starts based on RHEL9 CNV Builds

Additional info: