Description of problem:
device assignment code truncates the top byte of the MSIX table size when setting up capabilities for the guest.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. obvious coding error
won't see more than 256 MSIX vectors
match actual hw
Patch posted upstream:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Could you tell me how to verify this bug?
(In reply to comment #6)
> Hi, Alax
> Could you tell me how to verify this bug?
This issue was found by code review, so it may be difficult to actually test the boundary condition. You'd need a device that supported more than 256 vectors in it's MSIX table. I think it should be sufficient to verify there's no regression by testing a device that supports MSIX interrupts as an assigned device.