From: Alon Levy <alevy@redhat.com>
To: vrozenfe <990364@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 990364] Re: virtio_ioport_write: unexpected address 0x13 value 0x1
Date: Fri, 4 May 2012 09:42:45 +0200 [thread overview]
Message-ID: <20120504074245.GB19446@garlic.redhat.com> (raw)
In-Reply-To: <201205031516.58375.vrozenfe@redhat.com>
On Thu, May 03, 2012 at 12:16:57PM -0000, vrozenfe wrote:
> 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.
I get the same error with a vm that is virtio-net free:
qemu-system-x86_64 -chardev stdio,id=muxstdio,mux=on -mon chardev=muxstdio,mode=readline -vga qxl -drive file=/images/win7_squashed_earth.img,cache=unsafe,if=virtio,readonly=off -enable-kvm -L /home/alon/spice/upstream/share/qemu -m 2048 -cpu host -spice disable-ticketing,port=10001 -snapshot -no-shutdown -smp 2 -global qxl-vga.debug=1 -usb -device virtio-serial,multifunction=on -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -net none
I get it during bootup sometimes:
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 13 for device virtio-serial-bus.0
or
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2324003424 for device virtio-serial-bus.0
(0x8a857a60)
And also using a batch script to repeatedly disable and enable the
device, either with restarting the vdagent service or without.
With: endless-toggle-vdservice.bat
:loop
net stop vdservice
devcon disable "PCI\VEN_1AF4&DEV_1003"
devcon enable "PCI\VEN_1AF4&DEV_1003"
net start vdservice
goto :loop
I get some different error message as well:
qemu-system-x86_64: virtio-serial-bus: Guest failure in adding device virtio-serial-bus.0
But also the Unexpected port one:
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2351381636 for device virtio-serial-bus.0
(0x8c273c84)
The numbers are "random":
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 295259532 for device virtio-serial-bus.0
(0x11994d8c)
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 2671983748 for device virtio-serial-bus.0
(0x9f433c84)
And a lot of time it does work.
Without: endless-toggle-virtio.bat
:loop
devcon disable "PCI\VEN_1AF4&DEV_1003"
devcon enable "PCI\VEN_1AF4&DEV_1003"
goto :loop
(this takes a *lot* of iterations to reproduce - ~20 success for 1
failure. Probably worth looking at the exact number)
qemu-system-x86_64: virtio-serial-bus: Guest failure in adding device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 4 for device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Guest failure in adding device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 13 for device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Guest failure in adding device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 13 for device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Guest failure in adding device virtio-serial-bus.0
qemu-system-x86_64: virtio-serial-bus: Guest failure in adding device virtio-serial-bus.0
>
> > > Stefan
> > >
> > > On Sat, Apr 28, 2012 at 9:49 AM, Vitalis <workyz@gmail.com> 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-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
>
>
> ** Bug watch added: Red Hat Bugzilla #808654
> https://bugzilla.redhat.com/show_bug.cgi?id=808654
>
> --
> 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
>
next prev parent reply other threads:[~2012-05-04 7:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120428084925.330.52554.malonedeb@soybean.canonical.com>
[not found] ` <CAJSP0QXaE=EMST=PYNhmueTPvbFHXghy35SM8GUHf9zjnKwU0Q@mail.gmail.com>
[not found] ` <201204301917.11349.vrozenfe@redhat.com>
2012-05-03 12:16 ` [Qemu-devel] [Bug 990364] [NEW] virtio_ioport_write: unexpected address 0x13 value 0x1 Vadim Rozenfeld
2012-05-04 7:42 ` Alon Levy [this message]
2012-05-08 8:32 ` Yan Vugenfirer
2012-05-03 19:17 ` [Qemu-devel] [Bug 990364] " Vitalis
2012-05-03 19:49 ` vrozenfe
2012-05-21 22:42 ` Vitalis
2012-05-22 13:43 ` vrozenfe
2012-05-22 20:34 ` Vitalis
2012-05-23 10:37 ` vrozenfe
2012-05-23 12:02 ` Vitalis
2012-05-23 12:05 ` Vitalis
2012-05-23 12:47 ` vrozenfe
2012-05-23 13:01 ` Vitalis
2012-05-23 15:13 ` vrozenfe
2012-11-30 12:04 ` Vitalis
2012-12-21 0:17 ` Szilárd Páll
2013-01-08 11:51 ` Vitalis
2016-11-04 13:35 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120504074245.GB19446@garlic.redhat.com \
--to=alevy@redhat.com \
--cc=990364@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).