Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-22326

[2140808] Hyperv feature set to "enabled: false" prevents scheduling

    XMLWordPrintable

Details

    • CNV Virtualization Sprint 227, CNV Virtualization Sprint 228, CNV Virtualization Sprint 229
    • High

    Description

      Description of problem:
      When running on an AMD system, if a Windows VM is created using:
      hyperv:
      evmcs:
      enabled: false

      scheduling will fail due to:
      Node-Selectors: cpu-feature.node.kubevirt.io/vmx=true
      cpu-vendor.node.kubevirt.io/Intel=true

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

      How reproducible:
      Every time

      Steps to Reproduce:
      1. Create a VM w/ evmcs explicitly set to false, selected to run on an AMD node
      2. oc describe virt-launcher pod to see scheduling failure (node(s) didn't match Pod's node affinity/selector)

      Actual results:
      Virt-launcher pod cannot be scheduled.

      Expected results:
      If the feature is explicitly disabled, it should not prevent scheduling.

      Attachments

        Activity

          People

            bmordeha@redhat.com Barak Mordehai
            jhopper@redhat.com Jenifer Abrams
            Zhe Peng Zhe Peng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: