Description of problem:

In 4.14 release doc, https://docs.openshift.com/container-platform/4.14/virt/release_notes/virt-4-14-release-notes.html#virt-4-14-bug-fix , we have the below statement in the bug fix.

• In a heterogeneous cluster with different compute nodes, virtual machines that have HyperV Reenlightenment enabled can be scheduled on nodes that do not support timestamp-counter scaling (TSC) or have the appropriate TSC frequency. ( BZ#2151169)

 
However the behaviour has not changed and remains exactly the same as that of the previous version where VMI is labeled with the lowest TSC frequency and will be scheduled only on the nodes with higher frequencies if the CPU supports TSC scaling. So the below limitation still persists.
 

• In a heterogeneous cluster with different compute nodes, virtual machines that have HyperV Reenlightenment enabled cannot be scheduled on nodes that do not support timestamp-counter scaling (TSC) or have the appropriate TSC frequency. ({}BZ#2151169)
   

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

4.14 Release doc https://docs.openshift.com/container-platform/4.14/virt/release_notes/virt-4-14-release-notes.html#virt-4-14-bug-fix

Expected results:

4.14 should add back the limitation and remove the above statement from the bug fix.