Hide Forgot
Description of problem: Creation of Windows high performance VM fails because networkInterfaceMultiqueue is enabled but interface model is changed to e1000e Version-Release number of selected component (if applicable): OCP 4.10.0-0.nightly-2021-10-31-210828, CNV 4.10.0 How reproducible: 100% Steps to Reproduce: 1. Create a Windows VM using the wizard 2. Select Highperformance for workload Actual results: VM creation fails on: Error "virtio-net multiqueue request, but there are no virtio interfaces defined" for field "spec.template.spec.domain.devices.networkInterfaceMultiqueue" Expected results: VM creation should succeed Additional info: networkInterfaceMultiqueue is enabled but interface model is changed to e1000e Windows common template: interfaces: - masquerade: {} model: virtio name: default networkInterfaceMultiqueue: true Failed VM spec: apiVersion: kubevirt.io/v1 kind: VirtualMachine metadata: annotations: vm.kubevirt.io/validations: | [ { "name": "minimal-required-memory", "path": "jsonpath::.spec.domain.resources.requests.memory", "rule": "integer", "message": "This VM requires more memory.", "min": 536870912 }, { "name": "windows-virtio-bus", "path": "jsonpath::.spec.domain.devices.disks[*].disk.bus", "valid": "jsonpath::.spec.domain.devices.disks[*].disk.bus", "rule": "enum", "message": "virto disk bus type has better performance, install virtio drivers in VM and change bus type", "values": ["virtio"], "justWarning": true }, { "name": "windows-disk-bus", "path": "jsonpath::.spec.domain.devices.disks[*].disk.bus", "valid": "jsonpath::.spec.domain.devices.disks[*].disk.bus", "rule": "enum", "message": "disk bus has to be either virtio or sata or scsi", "values": ["virtio", "sata", "scsi"] }, { "name": "windows-cd-bus", "path": "jsonpath::.spec.domain.devices.disks[*].cdrom.bus", "valid": "jsonpath::.spec.domain.devices.disks[*].cdrom.bus", "rule": "enum", "message": "cd bus has to be sata", "values": ["sata"] } ] name.os.template.kubevirt.io/win2k19: Microsoft Windows Server 2019 labels: app: zzzz vm.kubevirt.io/template: windows2k19-highperformance-medium vm.kubevirt.io/template.revision: '1' vm.kubevirt.io/template.version: v0.16.2 os.template.kubevirt.io/win2k19: 'true' flavor.template.kubevirt.io/medium: 'true' workload.template.kubevirt.io/highperformance: 'true' vm.kubevirt.io/template.namespace: openshift name: zzzz namespace: default spec: dataVolumeTemplates: - metadata: name: zzzz-rootdisk-94b7e spec: pvc: accessModes: - ReadWriteOnce resources: requests: storage: 60Gi storageClassName: hostpath-provisioner volumeMode: Filesystem source: registry: url: 'docker://quay.io/kubevirt/fedora-cloud-container-disk-demo:latest' running: false template: metadata: annotations: vm.kubevirt.io/flavor: medium vm.kubevirt.io/os: windows2k19 vm.kubevirt.io/workload: highperformance labels: kubevirt.io/domain: zzzz kubevirt.io/size: medium vm.kubevirt.io/name: zzzz os.template.kubevirt.io/win2k19: 'true' flavor.template.kubevirt.io/medium: 'true' workload.template.kubevirt.io/highperformance: 'true' spec: domain: clock: timer: hpet: present: false hyperv: {} pit: tickPolicy: delay rtc: tickPolicy: catchup utc: {} cpu: cores: 1 dedicatedCpuPlacement: true isolateEmulatorThread: true sockets: 1 threads: 1 devices: disks: - bootOrder: 1 disk: bus: sata name: rootdisk - cdrom: bus: sata name: windows-guest-tools inputs: - bus: usb name: tablet type: tablet interfaces: - masquerade: {} model: e1000e name: default networkInterfaceMultiqueue: true features: acpi: {} apic: {} hyperv: reenlightenment: {} ipi: {} synic: {} synictimer: direct: {} spinlocks: spinlocks: 8191 reset: {} relaxed: {} vpindex: {} runtime: {} tlbflush: {} frequencies: {} vapic: {} machine: type: pc-q35-rhel8.4.0 resources: requests: memory: 4Gi evictionStrategy: LiveMigrate hostname: zzzz networks: - name: default pod: {} terminationGracePeriodSeconds: 3600 volumes: - dataVolume: name: zzzz-rootdisk-94b7e name: rootdisk - containerDisk: image: registry.redhat.io/container-native-virtualization/virtio-win name: windows-guest-tools
Verified on upstream master
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056