1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
debug: 0.825
register: 0.781
virtual: 0.745
device: 0.734
assembly: 0.732
semantic: 0.732
user-level: 0.716
permissions: 0.710
PID: 0.705
network: 0.703
kernel: 0.700
graphic: 0.686
VMM: 0.681
files: 0.658
architecture: 0.657
performance: 0.652
peripherals: 0.649
vnc: 0.631
KVM: 0.631
arm: 0.626
mistranslation: 0.619
TCG: 0.602
x86: 0.580
socket: 0.579
boot: 0.566
ppc: 0.552
hypervisor: 0.544
risc-v: 0.529
i386: 0.220
virtio-serial-bus: Unexpected port id
With qemu-kvm-0.15.0-rc1 virtio-serial-bus reports an error, and windows vdagent can not start. qemu-0.15.0-rc1 behaves as expected, ie vdagent runs in the guest, mouse passes seamlessly between spicec and host and copy/paste works between guest and host.
qemu-kvm has been configured with
./configure --target-list=x86_64-softmmu --disable-curses --disable-curl --audio-drv-list=alsa --audio-card-list=sb16,ac97,hda --enable-vnc-thread --disable-bluez --enable-vhost-net --enable-spice
and is started with
qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio,aio=native -m 1536 -name WinXP -net nic,model -net user -localtime -usb -vga qxl -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,nr=1,bus=virtio-serial0.0,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -monitor stdio
I've also tried start qemu like
qemu-system-x86_64 -cpu host -enable-kvm -pidfile /home/rick/qemu/hds/wxp.pid -drive file=/home/rick/qemu/hds/wxp.raw,if=virtio -m 768 -name WinXP -net nic,model=virtio -net user -localtime -usb -vga qxl -device virtio-serial -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -spice port=1234,disable-ticketing -monitor stdio
and observed the same results.
the host runs 2.6.39.4 vanilla kernel. the guest uses the most recent virtio-serial, vga-qxl and vdagent from spice-space.org
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
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.
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.
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
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
Triaging old bug tickets ... Can you still reproduce this problem with the latest version of QEMU?
[Expired for QEMU because there has been no activity for 60 days.]
This looks like https://bugzilla.redhat.com/show_bug.cgi?id=819412 which is about the same age.
|