Bug 2222009

Summary:	Warn when PCIe devices are plugged into non-zero slot of a downstream PCIe port
Product:	Red Hat Enterprise Linux 9	Reporter:	Ani Sinha <anisinha>
Component:	qemu-kvm	Assignee:	Ani Sinha <anisinha>
qemu-kvm sub component:	PCI	QA Contact:	Yiqian Wei <yiwei>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	jinzhao, juzhang, virt-maint
Version:	9.3	Keywords:	MigratedToJIRA, Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 18:10:49 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:

Description Ani Sinha 2023-07-11 13:46:27 UTC

Please see description in BZ 2128929.

The following combination is illegal as the address 0x2.0x5 is invalid on a pcie root port:

-device '{"driver":"pcie-root-port","port":21,"chassis":6,"id":"pci.6","bus":"pcie.0","addr":"0x2.0x5"}' \

{"execute":"device_add","arguments":{"driver":"virtio-net-pci","netdev":"hostnet1","mac":"00:11:22:33:44:03","id": "net1","bus":"pci.6","addr":"0x2.0x5"}}

Add a warning to let users know they are using an invalid configuration. 

This has already been fixed upstream with this commit:

https://gitlab.com/qemu-project/qemu/-/commit/ca92eb5defcf9d1c2106341744a73a03cf26e824

We can test this bug when we rebase QEMU to version 8.1 or above and mark it as fixed upon rebase.

Comment 3 RHEL Program Management 2023-09-22 18:09:28 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-22 18:10:49 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.