Bug 1244347 - Quirk for Chelsio T5 MSI-X PBA
Summary: Quirk for Chelsio T5 MSI-X PBA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Alex Williamson
QA Contact: Virtualization Bugs
Depends On:
Blocks: 1244348
TreeView+ depends on / blocked
Reported: 2015-07-17 20:35 UTC by Alex Williamson
Modified: 2015-11-19 05:11 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-1.5.3-98.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1244348 (view as bug list)
Last Closed: 2015-11-19 05:11:42 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2213 0 normal SHIPPED_LIVE qemu-kvm bug fix and enhancement update 2015-11-19 08:16:10 UTC

Description Alex Williamson 2015-07-17 20:35:14 UTC
Description of problem:
Chelsio T5 adapters incorrectly list the MSI-X Pending Bit Array (PBA) table at an offset beyond the PCI BAR containing it.  The guest does not use the PBA, but vfio does as part of mapping device regions for the guest.  When attempting to assign one of these devices to a VM, the call to msix_init() will fail due to this inconsistency.  A quirk has been added to the QEMU vfio-pci driver correct this problem in the case of a Chelsio T5 adapter and error with a useful message indicating a hardware problem in the general case.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Attempt to assign Chelsio T5 to a guest

Actual results:
Device fails to attach on hot plug, VM startup failure on cold plug (presumably, we don't have any)

Expected results:
Device attaches/VM starts

Additional info:
Upstream patch:

Comment 7 Miroslav Rezanina 2015-07-24 18:16:18 UTC
Fix included in qemu-kvm-1.5.3-98.el7

Comment 10 juzhang 2015-08-03 03:47:02 UTC
According to comment9, set this issue as verified.

Comment 12 errata-xmlrpc 2015-11-19 05:11:42 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.