This appears to address it in QEMU v2.4:
commit 6652d0811c9463fbfb2d2d1cb2ec03f388145c5f
Author: Jason Wang
Date: Wed May 27 16:26:07 2015 +0800
virtio-pci: don't try to mask or unmask vqs without notifiers
We should validate the vq index against nvqs_with_notifiers. Otherwise we
Looking through old bug tickets... can you still reproduce this issue
with the latest version of QEMU? Or could we close this ticket nowadays?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribe
I'm using 62.72.104.10300. I started with the old virtio-win-0.1-100
ISO, but I couldn't figure out how to downgrade to the latest "stable"
release, so instead I upgraded to the 103 release to see if it fixed
anything. It does not.
--
You received this bug notification because you are a member
Using almost the same XML but still could not reproduce this by myself.
What's the version of guest driver inside? I'm using 12/19/2014
62.70.104.9800?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1
Correction, I was using the stock distro qemu-kvm. Yes, the problem
occurs on a stock seabios win8.1 VM without vfio:
win8.1
896cb319-c196-4b92-a7e2-2306b0eac769
4194304
4194304
2
hvm
SandyBridge
The bug is unaffected, it still occurs, by removing the vfio devices
from the config and replacing them with a standard spice/qxl graphics
setup. I'm unable to reproduce the issue so far using a seabios-based
win8.1 install.
--
You received this bug notification because you are a member of qemu-
>From the trace, looks like the driver is trying to assign config vq (2)
an vector(2). This is interesting.
I try to reproduce but fail. (The only difference is my guest does not
have any vfio and ovmf was not used).
Can you reproduce it without ovmf and vfio?
Thanks
--
You received this bug n
