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.
This is a potential QEMU segfault, so I've cloned to qemu-kvm for RHEL.
Fixed by qemu.git b3e27c3aee8f5a96debfe0346e9c0e3a641a8516
A fairly effective test for this is to install the debuginfo package and run gdb on qemu before removing the device. Set a breakpoint on vfio_intx_interrupt. After removing the device with device_del or libvirt tools, vfio_intx_interrupt should not be called. In the failing case, it continues to be called with the opaque data for the deleted device. Since the error is continued use of an fd with freed data, reliable test cases can be temporary.
Comment 5Miroslav Rezanina
2015-01-25 17:27:47 UTC
QE tested bug with the latest qemu-kvm-1.5.3-86.el7.x86_64. The following are test scenarios and result.
S1. Assigned one GPU device(k1 or k2) to guest. then unhotplug it.
For windows(win7 64big) guest. qemu and guest work well
For RHEL7.1 guest. qemu and guest work well(guest kernel 3.10.0-226.el7.x86_64)
S2. Assigned two GPU devices(k1 and k2) to guest. then unhotplug one of them and restart guest.
result:guest kernel panic. I filed a new bug 1186194 to track it.
(In reply to FuXiangChun from comment #7)
> QE tested bug with the latest qemu-kvm-1.5.3-86.el7.x86_64. The following
> are test scenarios and result.
>
> S1. Assigned one GPU device(k1 or k2) to guest. then unhotplug it.
>
> For windows(win7 64big) guest. qemu and guest work well
>
> For RHEL7.1 guest. qemu and guest work well(guest kernel
> 3.10.0-226.el7.x86_64)
>
> S2. Assigned two GPU devices(k1 and k2) to guest. then unhotplug one of them
> and restart guest.
>
> result:guest kernel panic. I filed a new bug 1186194 to track it.
Additional info, I tested win7 guest as well, window guest does not hit this issue.
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://rhn.redhat.com/errata/RHSA-2015-0349.html