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
|
kernel: 0.888
peripherals: 0.857
user-level: 0.809
device: 0.750
architecture: 0.645
performance: 0.569
PID: 0.563
semantic: 0.421
register: 0.363
graphic: 0.321
ppc: 0.281
KVM: 0.271
mistranslation: 0.185
debug: 0.171
socket: 0.151
permissions: 0.144
files: 0.132
vnc: 0.128
x86: 0.114
boot: 0.096
virtual: 0.080
network: 0.065
VMM: 0.060
hypervisor: 0.050
assembly: 0.037
risc-v: 0.035
TCG: 0.030
arm: 0.024
i386: 0.023
-usbdevice tablet broken on win XP client
I'm using the qemu-kvm package from arch (not the qemu package), and on prior versions of qemu-kvm I was able to use -usbdevide tablet without problems. The absolute mouse position is great... With current version of qemu-kvm, when I use -usbdevice tablet, I got no mouse at all. As my client is windows XP, it's not good to try do anything without mouse, :-)
I searched in current bugs, and didn't find any bug which subject included "tablet", so I'm submitting this bug...
Current qemu-kvm package in arch I'm using is:
% pacman -Ss qemu-kvm
extra/qemu-kvm 0.15.0-2 [installed]
Latest KVM QEMU is a generic and open source processor emulator which achieves a good emulation speed by using dynamic translation.
Please notice I do not get any error, just the mouse broken...
thanks,
Javier.
Forgot to mention, I'm using linux 3.0.4, but the problem also is present on all 3.0.* kernels:
% pacman -Ss linux | 'grep' core
...
core/linux 3.0.4-1 (base) [installed]
And the kvm module used is the intel one:
% lsmod | 'grep' kvm
kvm_intel 53373 3
kvm 328912 1 kvm_intel
If more information is needed, please let me know...
Also observed on Fedora 16: https://bugzilla.redhat.com/show_bug.cgi?id=754149
Can you reproduce this problem with the latest version of QEMU from http://qemu-project.org/Download ?
According to the Fedora bug, this has been fixed. And since there wasn't any reply to the question in my last comment, I assume nobody experiences this issue anymore. So closing this ticket now...
|
