summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/105/graphic/1618301
blob: 3d8012951355ad34f44dcf2ca1b474887c43aa6f (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
54
55
56
57
58
59
60
61
62
63
64
graphic: 0.426
device: 0.400
other: 0.358
socket: 0.335
semantic: 0.222
instruction: 0.215
boot: 0.210
network: 0.198
vnc: 0.191
mistranslation: 0.174
KVM: 0.126
assembly: 0.106

qemu-input: Mouse stops working in Windows guest

ROCCAT Kone XTD mouse will randomly stop working in the guest until it's restarted.  Windows Event Viewer shows an error in i8042prt, with the message "Could not set the mouse resolution". The XML log:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="i8042prt" /> 
  <EventID Qualifiers="49157">23</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2016-08-30T02:52:00.354536300Z" /> 
  <EventRecordID>5708</EventRecordID> 
  <Channel>System</Channel> 
  <Computer>cronus</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data /> 
  <Binary>000008000100000000000000170005C03205000000000000000000000000000000000000000000000000000000000000</Binary> 
  </EventData>
  </Event>

Host is running Linux 4.7.2 with QEMU 2.6.1.

The same with:
 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux
QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-7)
and 

Windows 4.0 sp6 workstation.

This guest worked in virtualbox without issues.

Still exists in  QEMU emulator version 5.0.0 (Debian 1:5.0-5)  running on Linux  5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 GNU/Linux


Another observation  (not sure if 100% relevant) 
When I leave "Generic PS/2 mouse" as an ONLY pointing device, I can observe erratic moving ("jumping") cursor in (at least) windows guests (NT4 sp 6 , XP, Win 8.1)

QEMU emulator version 5.0.0 (Debian 1:5.0-6)



This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:

 https://gitlab.com/qemu-project/qemu/-/issues/126