Ladi Prosek writes:
> On Mon, Nov 13, 2017 at 3:22 PM, Markus Armbruster wrote:
>> Ladi Prosek writes:
>>
>>> As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
>>> QEMU crashes with:
>>>
>>> kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
>>>
>>> if the ivshm
On Mon, Nov 13, 2017 at 3:22 PM, Markus Armbruster wrote:
> Ladi Prosek writes:
>
>> As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
>> QEMU crashes with:
>>
>> kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
>>
>> if the ivshmem device is configured with mor
Ladi Prosek writes:
> As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
> QEMU crashes with:
>
> kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
>
> if the ivshmem device is configured with more vectors than what the server
> supports. This is caused by the ivs
Thanks Ladi, I had not yet had time to dig into these, this patch set
resolves all issues I was aware of.
Tested-by: Geoffrey McRae
On 2017-11-11 04:34, Ladi Prosek wrote:
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi
notifications"),
QEMU crashes with:
kvm_irqchip_commit_rou
- Original Message -
> As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
> QEMU crashes with:
>
> kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
>
> if the ivshmem device is configured with more vectors than what the server
> supports. This is caused
As of commit 660c97eef6f8 ("ivshmem: use kvm irqfd for msi notifications"),
QEMU crashes with:
kvm_irqchip_commit_routes: Assertion `ret == 0' failed.
if the ivshmem device is configured with more vectors than what the server
supports. This is caused by the ivshmem_vector_unmask() being called
