This looks like https://bugzilla.redhat.com/show_bug.cgi?id=819412
which is about the same age.
** Bug watch added: Red Hat Bugzilla #819412
https://bugzilla.redhat.com/show_bug.cgi?id=819412
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/821078
Title:
Triaging old bug tickets ... Can you still reproduce this problem with
the latest version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On (Tue) 28 Jul 2015 [09:17:25], Quwj wrote:
I met two bugs above.QEMU version is 2.1.3 and VM is Windows7.
QEMU Log is:
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 15819934 for device
virtio-serial0.0
(snip)
Bug description:
With qemu-kvm-0.15.0-rc1 virtio-serial-bus
I met two bugs above.QEMU version is 2.1.3 and VM is Windows7.
QEMU Log is:
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 15819934 for device
virtio-serial0.0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I can confirm this Bug with qemu 1.0 using a Windows7 or Windows 2003 virtual
machine.
After connecting 1-10 times the agent stops working.
Sometimes it helps to restart the VD Service within the vm.
Qemu Log shows:
dispatch_vdi_port_data: invalid port
--
You received this bug notification
Using qemu-kvm-0.15.0 for a few weeks now, I'd like to report that maybe
1/10 times it works as expected: ie, there is no virtio-serial-bus
error, vdagent in the windows guest starts, etc.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
This continues to occur with qemu-kvm 0.15 on only one of my WXP VMs.
The fact that one of them works fine led me to believe it was a windows
issue (or spice), but the fact that both work fine with straight qemu
indicates that there is something with qemu-kvm involved in the problem.
--
You
sorry, the output from qemu-kvm which seems to indicate an error is
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 3125770964 for device
virtio-serial0.0
or sometimes
qemu-system-x86_64: virtio-serial-bus: Unexpected port id 47936 for device
virtio-serial0.0
--
You received this bug
