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.
Errno 17 is EEXIST, vIOMMU probably didn't invalidate all the mappings from the DPDK domain before the device was added back to the static identity domain.
(In reply to Alex Williamson from comment #3)
> Errno 17 is EEXIST, vIOMMU probably didn't invalidate all the mappings from
> the DPDK domain before the device was added back to the static identity
> domain.
Agreed.
It's very possible that we didn't handle the case where the context entry switches from valid to invalid. In that case now we might ignore the shadow sync but actually we should do a "unmap all" instead.
I'm preparing a package for test. Will update soon.
(In reply to Peter Xu from comment #6)
> I made a mistake on building previous package... Please instead try this one:
>
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=18303752
>
> Please make sure that the package is suffixed with bz1627272_2 not bz1627272.
Peter, this bug has gone with above build. Thanks.
Versions:
3.10.0-945.el7.x86_64
qemu-kvm-rhev-2.12.0-15.el7.bz1627272_2.x86_64
Testings:
Testing with both PF and VF, following same steps of Description, everything works well as expected.
- Qemu works well
- No any error in both host and guest #dmesg
- testpmd in guest can receive packets.
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-2019:2553