virtio_ioport_write: unexpected address 0x13 value 0x1

[Vitalis]

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 da607499-1d8f-e7ef-d1d2-38
1c1839e4ba -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
,cache=none -drive file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net tap,fd=43,vlan=0,name=tap.0 -serial
none -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus
pci_add_option_rom: failed to find romfile "pxe-virtio.bin"

with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012 x86_64 GNU/Linux
qemu drivers are virtio-win-0.1-22.iso
kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
qemu 0.12.3+noroms-0ubuntu9.18

[Vitalis (workyz)]

I forgot: guest os is Windows XP Pro SP3

[Stefan Hajnoczi (stefanha)]

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 <email address hidden> wrote:
> 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 da607499-1d8f-e7ef-d1d2-38
> 1c1839e4ba -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> ,cache=none -drive file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net tap,fd=43,vlan=0,name=tap.0 -serial
> none -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus
> pci_add_option_rom: failed to find romfile "pxe-virtio.bin"
>
> with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012 x86_64 GNU/Linux
> qemu drivers are virtio-win-0.1-22.iso
> kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> qemu 0.12.3+noroms-0ubuntu9.18
>
> ** Affects: qemu
>     Importance: Undecided
>         Status: New
>
>
> ** Tags: bug kvm virtio
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/990364
>
> Title:
>  virtio_ioport_write: unexpected address 0x13 value 0x1
>
> Status in QEMU:
>  New
>
> Bug description:
>  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 da607499-1d8f-e7ef-d1d2-38
>  1c1839e4ba -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
>  ,cache=none -drive file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net tap,fd=43,vlan=0,name=tap.0 -serial
>  none -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus
>  pci_add_option_rom: failed to find romfile "pxe-virtio.bin"
>
>  with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012 x86_64 GNU/Linux
>  qemu drivers are virtio-win-0.1-22.iso
>  kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
>  qemu 0.12.3+noroms-0ubuntu9.18
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/990364/+subscriptions
>

[vrozenfe (vrozenfe)]

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 Sat, Apr 28, 2012 at 9:49 AM, Vitalis <email address hidden> wrote:
> > 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 da607499-1d8f-e7ef-d1d2-38 1c1839e4ba
> > -chardev
> > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowa
> > it -monitor chardev:monitor -localtime -boot c -drive
> > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > ,cache=none -drive
> > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,forma
> > t=raw -net
> > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > to find romfile "pxe-virtio.bin"
> >
> > with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012
> > x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> > kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> > qemu 0.12.3+noroms-0ubuntu9.18
> >
> > ** Affects: qemu
> > Importance: Undecided
> > Status: New
> >
> >
> > ** Tags: bug kvm virtio
> >
> > --
> > You received this bug notification because you are a member of qemu-
> > devel-ml, which is subscribed to QEMU.
> > https://bugs.launchpad.net/bugs/990364
> >
> > Title:
> > virtio_ioport_write: unexpected address 0x13 value 0x1
> >
> > Status in QEMU:
> > New
> >
> > Bug description:
> > 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 da607499-1d8f-e7ef-d1d2-38 1c1839e4ba
> > -chardev
> > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,nowa
> > it -monitor chardev:monitor -localtime -boot c -drive
> > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > ,cache=none -drive
> > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,forma
> > t=raw -net
> > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > to find romfile "pxe-virtio.bin"
> >
> > with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC 2012
> > x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> > kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> > qemu 0.12.3+noroms-0ubuntu9.18
> >
> > To manage notifi...

[vrozenfe (vrozenfe)]

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 Stefan,
> Yes, it's on my radar.
> Cheers,
> Vadim.
>
seems to be ndis related
(https://bugzilla.redhat.com/show_bug.cgi?id=808654#c10)
cc'ing Yan.

> > Stefan
> >
> > On Sat, Apr 28, 2012 at 9:49 AM, Vitalis <email address hidden> wrote:
> > > 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 da607499-1d8f-e7ef-d1d2-38
> > > 1c1839e4ba -chardev
> > > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,now
> > > a it -monitor chardev:monitor -localtime -boot c -drive
> > > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > > ,cache=none -drive
> > > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,form
> > > a t=raw -net
> > > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > > tablet -vnc 127.0.0.1:3 -k en-us -vga cirrus pci_add_option_rom: failed
> > > to find romfile "pxe-virtio.bin"
> > >
> > > with kernel 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56 UTC
> > > 2012 x86_64 GNU/Linux qemu drivers are virtio-win-0.1-22.iso
> > > kvm version 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.18
> > > qemu 0.12.3+noroms-0ubuntu9.18
> > >
> > > ** Affects: qemu
> > >
> > > Importance: Undecided
> > >
> > > Status: New
> > >
> > > ** Tags: bug kvm virtio
> > >
> > > --
> > > You received this bug notification because you are a member of qemu-
> > > devel-ml, which is subscribed to QEMU.
> > > https://bugs.launchpad.net/bugs/990364
> > >
> > > Title:
> > > virtio_ioport_write: unexpected address 0x13 value 0x1
> > >
> > > Status in QEMU:
> > > New
> > >
> > > Bug description:
> > > 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 da607499-1d8f-e7ef-d1d2-38
> > > 1c1839e4ba -chardev
> > > socket,id=monitor,path=/var/lib/libvirt/qemu/nata_xp.monitor,server,now
> > > a it -monitor chardev:monitor -localtime -boot c -drive
> > > file=/root/nata_xp.qcow2,if=virtio,index=0,boot=on,format=raw
> > > ,cache=none -drive
> > > file=/home/admino/virtio-win-0.1-22.iso,if=ide,media=cdrom,index=2,form
> > > a t=raw -net
> > > nic,macaddr=00:16:36:06:02:69,vlan=0,model=virtio,name=virtio.0 -net
> > > tap,fd=43,vlan=0,name=tap.0 -serial none -parallel none -usb -usbdevice
> > > tablet -vnc 127.0.0.1:3 -k en-u...

[Vitalis (workyz)]

And what? Where can I get new drivers for WinXP?

[vrozenfe (vrozenfe)]

On Thursday, May 03, 2012 10:17:15 PM Vitalis wrote:
> And what? Where can I get new drivers for WinXP?

http://people.redhat.com/vrozenfe/build-27/virtio-win-prewhql-0.1.zip

[Vitalis (workyz)]

But with new drivers i got "virtio_ioport_write: unexpected address 0x13 value 0x1" again.

[vrozenfe (vrozenfe)]

can you upload the corresponding dump file?

[Vitalis (workyz)]

I see in properties of drivers version 51.63.103.2700 (date is 20.04.2012).

[vrozenfe (vrozenfe)]

It doesn't look like as a vritio-win driver problem.
you get the following message
"virtio_ioport_write: unexpected address 0x13 value 0x1"
because netkvm driver triggers BSOD event, which happened in
different stack, and then kills the hosting QEMU prccess
by writing to ISR register.

In your case (minidumps in comments #1 and #11) BSOD
happened inside of Raw Input Thread, which usually caused
by all kind of key and mouse filters/loggers.

Unfortunately minidump doesn't provide enough information
to troubleshoot such kind of problems. If it's possible - try disabling
antivirus and RDP on your system.
Vadim.

[Vitalis (workyz)]

I change network card in guest to RTL and no have BSOD, on all guest. Why?
How can we detect the cause?

[Vitalis (workyz)]

and how can i use winXP without antivirus and RDP? Its nonsense!!! :-) no sense!

[vrozenfe (vrozenfe)]

Hard to say at the moment.
In both cases the crash stack looks absolutely the same:

nt!KiDeliverApc+0x66
hal!HalpApcInterrupt+0xc5
hal!HalRequestSoftwareInterrupt+0x3b
win32k!RawInputThread+0x625
win32k!xxxCreateSystemThreads+0x60
win32k!NtUserCallOneParam+0x23
nt!KiFastCallEntry+0xf8

Try reproducing the problem with Kernel
memory dump option turned on instead of
minidump. In this case it will be possible
to extract more useful information.

Vadim.

[Vitalis (workyz)]

How turn on kernel memory dump in XP?

[vrozenfe (vrozenfe)]

http://support.microsoft.com/kb/316450

[Vitalis (workyz)]

Hello!
ANd again "virtio_ioport_write: unexpected address 0x13 value 0x1".
Drvers: from virtio-win-0.1-30.iso
config: <domain type='kvm'>
  <name>buh_xp</name>
  <uuid>f0e8ac00-4545-eb5d-e8f2-c885063e5ad0</uuid>
  <memory>1097152</memory>
  <currentMemory>1097152</currentMemory>
  <vcpu>1</vcpu>
  <os>
    <type arch='i686' machine='pc-0.12'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
  </features>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/root/buh_xp.qcow2'/>
      <target dev='hda' bus='virtio'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/worky/virtio-win-0.1-30.iso'/>
      <target dev='hdc' bus='ide'/>
      <readonly/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:36:2f:11:31'/>
      <source bridge='br0'/>
      <model type='virtio'/>
    </interface>
    <console type='pty'>
      <target port='0'/>
    </console>
    <console type='pty'>
      <target port='0'/>
    </console>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
    <video>
      <model type='cirrus' vram='9216' heads='1'/>
    </video>
  </devices>
</domain>

uname: Linux test-2 2.6.32-43-server #97-Ubuntu SMP Wed Sep 5 16:56:41 UTC 2012 x86_64 GNU/Linux
qemu-kvm: 0.12.3+noroms-0ubuntu9.20
kvm: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.20
hardware: SuperMicro x8sil-f

[Szilárd Páll (sin-pecado)]

I can't add much, except that I started noticing his issue when migrating my VMs to an Ubuntu Precise server hypervisor where under (heavy?) load my Win 2008 Server VM started to crash very frequently with the error showing up in the libvirt log of the VM.

It might be useful information that I ended up moving the VM back to a Debian Squeeze hypervisor which hosted it originally and things were running smoothly until earlier today when a crash with the same message happened again. What's sure is that under Squeeze the issue is far-far less frequent, on Precise the VM got reset a dozen times during the first 48 h, while on Squeeze it's been running fine even under heavy load for weeks without a hiccup.

Details of the Precise hypervisor:
kvm: 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.3
qemu-kvm: 1.0+noroms-0ubuntu14.3
kernel: 3.2.0-32-generic
(tested with virtio drivers virtio-win-0.1-15.iso and virtio-win-0.1-30.iso)

Details of the Squeeze hypervisor:
kvm: 1:0.12.5+dfsg-5+squeeze8
qemu-kvm: 0.12.5+dfsg-5+squeeze8
kernel: 2.6.32-5-amd64
(tested with virtio drivers virtio-win-0.1-15.iso)

[Vitalis (workyz)]

IMHO, Ubuntu Server for KVM virtualization - is BAD idea! Very BAD idea......

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

Hi,
this got to my attention after being reassigned from upstream to Ubuntu's qemu.

I'd assume that this is very much timed out and no more applicable and mark it incomplete by that to give everybody a chance to object and describe what they face today.