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:
PCI bridge has minimal slot '1'. PCI device attached to pci bridge
is auto-assigned invalid PCI address 0000:01:00.0. But slot must be >= 1


Version-Release number of selected component (if applicable):
libvirt-2.0.0-5.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. define a guest with 1 disk which is attached to pci bridge
<disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/mnt/nfs2/RHEL-7.3-latest.qcow2'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' bus='0x1'/>
    </disk>

<controller type='pci' index='0' model='pci-root'/>
 <controller type='pci' index='1' model='pci-bridge'>
      <address type='pci' bus='0x0'/>
</controller>

# virsh define vm1-pxb.xml
error: Failed to define domain from vm1-pxb.xml
error: XML error: Invalid PCI address 0000:01:00.0. slot must be >= 1

2.
3.

Actual results:
PCI device attached to pci bridge is auto-assigned PCI address 0000:01:00.0,
but minimal slot of pci bridge is 1


Expected results:
In this case, slot must be >=1 in auto-assigned pci address


Additional info:

There is no auto-assignment happening here, because you've specified a bus. Once you've specified anything beyond just <address type='pci'> (which itself only exists to allow disambiguation between pci and mmio on machinetypes that support both, e.g. aarch64), you have chosen the PCI address yourself. the domain, bus, slot, and function attributes are all optional, and default to 0 if not specified, so if you say:

   <address type='pci' bus='1'/>

that means

   <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>

If you want to force the device to be on bus 1, then you need to specify everything in the address that isn't 0.