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.
Please re-test with recent kernel and qemu packages. Attempt to reproduce this
on the following environment failed.
Kernel: 3.10.0-71.el7.x86_64
qemu: qemu-kvm-1.5.3-37.el7.x86_64
Thanks
-vlad
Re-tested this bug with qemu-kvm-1.5.3-37.el7.x86_64 and 3.10.0-73.el7.x86_64.
Test steps as comment2.
result: fail to boot guest when attach more than 4 devices to the same switch.
so, This bug still can be reproduced with the latest qemu-kvm and kernel.
This only happens with q35. This also only happens when you have more then 5 devices each hanging off its won pcie down port. In the reproducer from
Comment 2, we have 5 devices, each using bus downstream1-5. The fact that
some of them are virtio_net and others are virtio_scsi doesn't seem to
matter. The scsi device isn't detected either.
Interestingly, connecting them all to a single downstream bus makes things work
again. Even distributing them to 4 downstream buses still works. It's when we
hit downstream5 is where we have a problem.
After looking at what iPXE does, it looks like it is trying to access the vq.
Attempting to trap in virtio_pci_config_write() succeeds when using a working
configuration and fails when using a non-working set-up. It looks like when
there are 5 downstream buses being used, qemu doesn't correctly locate the virtio memory region. Currently trying to debug this and determine where
the memory access ends up. It isn't virtio as its supposed to be.
-vlad
Verified that solution to Bug 1055832 also solves this issue. Changing component to seabios and marking as duplicate.
*** This bug has been marked as a duplicate of bug 1055832 ***