OpenShift Virtualization reports no nodes are available, cannot start VMs

Solution Verified - Updated -

Issue

  • OpenShift Virtualization report Insufficient devices.kubevirt.io/kvm.
  • OpenShift Virtualization doesn't work on AWS
  • Linux Virtual Machines are not not scheduling on worker nodes with one of the following messages
'0/9 nodes are available: 9 Insufficient devices.kubevirt.io/kvm, 9 node(s) didn''t match node selector.'
  • Windows Virtual Machines Machines are not not scheduling on worker nodes with one of the following messages
0/6 nodes are available: 3 node(s) didn't match Pod's node affinity/selector, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
  • kubevirt-node-labeller pods are stuck in a Pending state.

Environment

  • Red Hat OpenShift Container Platform 4.x
    • OpenShift Virtualization 2.x, 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content