Description of problem:
Windows VM was migratable in CNV 4.10.7, but after upgrade to 4.11.3 it becomes non-migratable, here the events from VMI:

1. VM Created and successfully migrated for the first time:
   > Normal SuccessfulCreate 49m disruptionbudget-controller Created PodDisruptionBudget kubevirt-disruption-budget-56ncf
   > Normal SuccessfulCreate 49m virtualmachine-controller Created virtual machine pod virt-launcher-windows-vm-1675645478-4397972-dsmmn
   > Normal Created 48m virt-handler VirtualMachineInstance defined.
   > Normal Started 48m virt-handler VirtualMachineInstance started.
   > Normal SuccessfulCreate 14m disruptionbudget-controller Created Migration kubevirt-evacuation-7frcx
   > Normal SuccessfulUpdate 14m virtualmachine-controller Expanded PodDisruptionBudget kubevirt-disruption-budget-56ncf
   > Normal PreparingTarget 11m (x2 over 11m) virt-handler VirtualMachineInstance Migration Target Prepared.
   > Normal PreparingTarget 11m virt-handler Migration Target is listening at 10.131.0.119, on ports: 35055,36327
   > Normal Migrating 11m (x5 over 11m) virt-handler VirtualMachineInstance is migrating.
   > Normal Migrated 11m virt-handler The VirtualMachineInstance migrated to node cnv-qe-infra-07.cnvqe2.lab.eng.rdu2.redhat.com.
   > Normal Deleted 11m virt-handler Signaled Deletion
   > Normal SuccessfulUpdate 11m disruptionbudget-controller shrank PodDisruptionBudget%!(EXTRA string=kubevirt-disruption-budget-56ncf)

1. When CNV upgraded - this message appeared:
   > Warning Migrated 5m32s virt-handler EvictionStrategy is set but vmi is not migratable; HyperV Reenlightenment VMIs cannot migrate when TSC Frequency is not exposed on the cluster: guest timers might be inconsistent
   > Warning Migrated 47s (x8 over 5m32s) virt-handler EvictionStrategy is set but vmi is not migratable; HyperV Reenlightenment VMIs cannot migrate when TSC Frequency is not exposed on the cluster: guest timers might be inconsistent

And VM is not migratable anymore.

Version-Release number of selected component (if applicable):
CNV 4.11.3

Steps to Reproduce:
1. Install CNV 4.10.7
2. Create Windows VM with HyperV Reenlightenment flag enabled
3. Upgrade CNV to 4.11.3

Actual results:
VM is not migratable after upgrade

Expected results:
VM should be migratable

Additional info:
Restarting VM after upgrade (`virtctl restart`) helps fix that