summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/KVM/1642011
blob: ab2b06d1d8fb10037537d6159891e3620b8eeac0 (plain) (blame)
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
KVM: 0.955
x86: 0.951
PID: 0.940
user-level: 0.931
device: 0.930
i386: 0.924
network: 0.900
virtual: 0.899
graphic: 0.883
socket: 0.856
peripherals: 0.848
architecture: 0.803
vnc: 0.782
files: 0.782
semantic: 0.772
performance: 0.754
permissions: 0.749
mistranslation: 0.739
debug: 0.728
hypervisor: 0.723
register: 0.680
ppc: 0.668
kernel: 0.626
boot: 0.588
risc-v: 0.559
arm: 0.498
VMM: 0.472
TCG: 0.448
assembly: 0.415

Mouse wheel events not forwarded to guest using GTK display

Using QEMU 2.7.0 with KVM enabled, when I launch the guest without options (using the default of gtk), the mouse wheel events are not propagated to the guest.

When I start qemu using -display sdk, mouse wheel events are properly forwarded.

I can determine that the guest is not receiving mouse wheel events by doing cat /dev/input/by-id/usb-QEMU_QEMU_USB_Mouse_42-event-mouse. When I scroll the wheel, no output is printed to the screen.

The guest is ChromiumOS.

The command line is:

qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -vga cirrus -usbdevice mouse -pidfile /tmp/kvm.pid -chardev pipe,id=control_pipe,path=/tmp/kvm.pipe -serial file:/tmp/kvm.serial -mon chardev=control_pipe -net nic,model=virtio -net user,hostfwd=tcp:127.0.0.1:9222-:22 -drive file=chromiumos/src/build/images/amd64-generic/latest/chromiumos_qemu_image.bin,index=0,media=disk,cache=unsafe

(Most of that invocation sets up Linux fifos for various and nefarious purposes and can be profitably ignored).

The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting all older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience.


[Expired for QEMU because there has been no activity for 60 days.]