Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
libvirt allow set busNr and numa node for a pci-bridge but won't use it
Version-Release number of selected component (if applicable):
libvirt-2.0.0-5.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepare a guest have a xml like this:
<controller type='pci' index='1' model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='1' busNr='254'>
<node>1</node>
</target>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</controller>
<controller type='ide' index='0'>
2. start guest:
# virsh start r7-lhuang
Domain r7-lhuang started
3. check qemu cmdline:
# ps aux|grep qemu
-device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x3
4. check active xml:
# virsh dumpxml r7-lhuang
...
<controller type='pci' index='1' model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='1' busNr='254'>
<node>1</node>
</target>
<alias name='pci.1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</controller>
...
Actual results:
Libvirt still show the numa node and busNr in active guest xml but didn't use it to build qemu cmd line for pci-bridge (this is a negative test case since pci-bridge won't use these element).
Expected results:
maybe report error during start guest ?
Additional info:
I just realized this was fixed in commit 5bd876, which will be in libvirt-4.2.0
commit 5bd8764ee087f8fe417db8d80d51e2d4cd57dc6e
Author: Andrea Bolognani <abologna>
Date: Tue Feb 20 15:12:37 2018 +0100
qemu: Validate PCI controller options (busNr)
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, 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-2018:3113
Description of problem: libvirt allow set busNr and numa node for a pci-bridge but won't use it Version-Release number of selected component (if applicable): libvirt-2.0.0-5.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare a guest have a xml like this: <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1' busNr='254'> <node>1</node> </target> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='ide' index='0'> 2. start guest: # virsh start r7-lhuang Domain r7-lhuang started 3. check qemu cmdline: # ps aux|grep qemu -device pci-bridge,chassis_nr=1,id=pci.1,bus=pci.0,addr=0x3 4. check active xml: # virsh dumpxml r7-lhuang ... <controller type='pci' index='1' model='pci-bridge'> <model name='pci-bridge'/> <target chassisNr='1' busNr='254'> <node>1</node> </target> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> ... Actual results: Libvirt still show the numa node and busNr in active guest xml but didn't use it to build qemu cmd line for pci-bridge (this is a negative test case since pci-bridge won't use these element). Expected results: maybe report error during start guest ? Additional info: