You had a BSOD on a guest.
NetKVM driver will write 1 to VIRTIO_PCI_ISR register in case of BSOD (we had
BSOD callback in the driver). The callback will be called on any BSOD, so it
doens't mean that the BSOD was due to virtio-net.
Check the guest and check if there is memory dump available.
On Monday, April 30, 2012 07:17:09 PM Vadim Rozenfeld wrote:
On Monday, April 30, 2012 03:31:03 PM Stefan Hajnoczi wrote:
Hi Vadim,
Here is a recent bug report with virtio-win-0.1-22.iso. Wanted to
bring it to your attention, please let me know if you already monitor
these bug emails.
Hi Vadim,
Here is a recent bug report with virtio-win-0.1-22.iso. Wanted to
bring it to your attention, please let me know if you already monitor
these bug emails.
Stefan
On Sat, Apr 28, 2012 at 9:49 AM, Vitalis wor...@gmail.com wrote:
Public bug reported:
Hello! I have:
On Monday, April 30, 2012 03:31:03 PM Stefan Hajnoczi wrote:
Hi Vadim,
Here is a recent bug report with virtio-win-0.1-22.iso. Wanted to
bring it to your attention, please let me know if you already monitor
these bug emails.
Hi Stefan,
Yes, it's on my radar.
Cheers,
Vadim.
Stefan
On
Public bug reported:
Hello! I have:
virtio_ioport_write: unexpected address 0x13 value 0x1
on config:
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 3072
-smp 1 -name nata_xp -uuid
