Description of problem:

Its not possible to disable IRQs for KubeVirt pods, on a per-pod basis ("irq-load-balancing.crio.io: disabled", as documented in the Performance Addon Operator documentation).

This might require use of globallyDisableIrqLoadBalancing=true, which globally disables irqs for any isolated CPUs of a worker node (and therefore any non-infrastructure pods scheduled on that node).

This might reduce performance of pods deployed on such worker nodes.

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

Steps to Reproduce:

Start a KubeVirt pod with "irq-load-balancing.crio.io: disabled" annotation,
feature won't be functional (CPUs assigned to such a KubeVirt pod will not be protected
from IRQs of the host system).

1.
2.
3.

Actual results:

Expected results:

That for KubeVirt pods with "irq-load-balancing.crio.io: disabled" annotation, the CPUs assigned for the pod have no IRQs which can be fired on them.

Additional info: