Bug 2070050
| Summary: | [4.10.1] Custom guest PCI address and boot order parameters are not respected in a list of multiple SR-IOV NICs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Orel Misan <omisan> | ||||
| Component: | Networking | Assignee: | Orel Misan <omisan> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yossi Segev <ysegev> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.10.0 | CC: | cnv-qe-bugs, gveitmic, phoracek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.10.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | virt-launcher v4.10.1-7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 2070136 (view as bug list) | Environment: | |||||
| Last Closed: | 2022-05-18 20:27:35 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2070136, 2070772, 2072942 | ||||||
| Attachments: |
|
||||||
|
Description
Orel Misan
2022-03-30 11:25:23 UTC
Any workarounds we could document here besides not adding pciAddress to the spec? Note there is no need to set custom PCI addresses on all SR-IOV NICs.
Just on the last one seems to be enough for the closure bug to replicate it to all:
interfaces:
- macAddress: 02:2d:47:00:00:02
model: virtio
name: nic-0
sriov: {}
- macAddress: 02:2d:47:00:00:03
model: virtio
name: nic-1
pciAddress: 0000:82:00.0
sriov: {}
server error. command SyncVMI failed: "LibvirtError(Code=27, Domain=20, Message='XML error: Attempted double use of PCI Address 0000:82:00.0')"
The fix was merged on upstream (https://github.com/kubevirt/kubevirt/pull/7478). Waiting for M/S patch to pass https://code.engineering.redhat.com/gerrit/c/kubevirt/+/401398/ Verified on CNV v4.10.1 (HCO v4.10.1-19), virt-launcher v4.10.1-8 1. Apply the attached SriovNetworkNodePolicy and SriovNetworks. [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ oc apply -f sriov-policy.yaml oc apply -f sriov-nesriovnetworknodepolicy.sriovnetwork.openshift.io/test-sriov-policy created [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ oc apply -f sriov-network1.yaml sriovnetwork.sriovnetwork.openshift.io/sriov-test-network1 created [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ oc apply -f sriov-network2.yaml sriovnetwork.sriovnetwork.openshift.io/sriov-test-network2 created 2. Apply the attached VirtualMachine, which has 2 secondary SR-IOV-based NICs, with a hard-coded PCI address set to the second one: [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ oc create ns sriov-test-sriov namespace/sriov-test-sriov created [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ oc apply -f sriov-vm1.yaml virtualmachine.kubevirt.io/sriov-vm1 created 3. Verify that the VM starts and runs successfully: [cnv-qe-jenkins@cnvqe-01 bz-2070050]$ oc get vmi -w NAME AGE PHASE IP NODENAME READY sriov-vm1 3s Scheduling False sriov-vm1 7s Scheduled cnvqe-10.lab.eng.tlv2.redhat.com False sriov-vm1 11s Scheduled cnvqe-10.lab.eng.tlv2.redhat.com False sriov-vm1 11s Running 10.128.3.90 cnvqe-10.lab.eng.tlv2.redhat.com False sriov-vm1 11s Running 10.128.3.90 cnvqe-10.lab.eng.tlv2.redhat.com True 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 Virtualization 4.10.1 Images security and bug fix 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:4668 |