My believe is that this bug can be closed. We have tested QEMU 1.4.x and
1.5.x series (with pci-assign) and at least these works fine.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to Q
I'm currently trying to make that happen, starting with the patches in
comments 2 & 3 and moving to something like the patch in comment 8 in
the development branch.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpa
Just a silly questions, because I don't know the deveploment process in
QEMU project -- can be your patches commited into project's VCS so that
new stable release contains them and doesn't fail again? Thank you!
--
You received this bug notification because you are a member of qemu-
devel-ml, wh
Confirmed, third patch for legacy pci-assign enables only 4 vectors on
host and guest. Mellanox IB works for me fine as well. Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1091766
Title:
Ph
On Wed, Dec 19, 2012 at 5:46 PM, Alex Williamson
wrote:
> You're right, I'm thinking of MSI where lspci reports x/y vectors. The
> only way I know to get this is to grep /proc/interrupts on host and
> guest. Look for kvm or vfio in the host and likely some device specific
> identifier in the gue
Here's another version of the legacy pci-assign patch. This should also
only use 4 vectors on the host, like vfio. I'm a little uneasy about
setting up an MSIMessage with unknown data, but I guess we did it for a
long time previously. Please test. Thanks
** Attachment added: "v2: pci-assign: E
You're right, I'm thinking of MSI where lspci reports x/y vectors. The
only way I know to get this is to grep /proc/interrupts on host and
guest. Look for kvm or vfio in the host and likely some device specific
identifier in the guest.
I also see your original log now, so old qemu worked, but wa
On Wed, Dec 19, 2012 at 4:31 PM, Alex Williamson
wrote:
> So you likely see through lspci that both the guest and host have 4
> vectors enabled.
Maybe you'll have to kick me on how to find this data. If I look on
lspci output, I find only this relevant thing:
Capabilities: [9c] MSI-X: Ena
VFIO is doing what I expect, growing the enabled vectors as each is
unmasked. It starts from 1 and has to disable and re-enable each time
it grows, so we have:
| vfio-pci :20:00.0: irq 150 for MSI/MSI-X
1
| vfio-pci :20:00.0: irq 150 for MSI/MSI-X
| vfio-pci :20:00.0: irq 151 for MS
Both patches against qemu 1.3 *works*, first with traditional PCI
pass., second with VFIO. Mellanox IB card in guest works fine again.
Great early Christmas present, thank you!
Just FYI: between both ways I can see little difference on host system
regarding the numbers of IRQs for MSI/MSI-X:
* VF
If the above pci-assign patch works, please also try this vfio-pci
version as it requires a slightly different implementation. Also
against qemu 1.3. Thanks.
** Attachment added: "vfio-pci: Make host MSI-X enable track guest"
https://bugs.launchpad.net/qemu/+bug/1091766/+attachment/3463505/+f
Does the attached patch against qemu 1.3 fix it for pci-assign?
** Attachment added: "pci-assign: Enable MSIX on device to match guest"
https://bugs.launchpad.net/qemu/+bug/1091766/+attachment/3463375/+files/foo
--
You received this bug notification because you are a member of qemu-
devel-ml,
12 matches
Mail list logo
