summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/peripherals/1496384
blob: b431d32425f473da612985d33f6ecb2fd65d327d (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
peripherals: 0.813
x86: 0.756
device: 0.718
boot: 0.700
architecture: 0.671
socket: 0.579
semantic: 0.575
graphic: 0.475
ppc: 0.460
performance: 0.415
register: 0.411
PID: 0.408
kernel: 0.387
permissions: 0.376
network: 0.369
user-level: 0.335
files: 0.330
assembly: 0.311
VMM: 0.307
hypervisor: 0.275
risc-v: 0.271
debug: 0.268
vnc: 0.257
mistranslation: 0.255
TCG: 0.225
virtual: 0.225
arm: 0.208
i386: 0.127
KVM: 0.050

Error 0x5D in Qemu for Windows 

The reason to use qemu for Windows is that the mouse in emulated Windows works well while it is unusable in  qemu at Ubuntu. 
Alternative solution/bug is mouse usability in qemu for Linux.
Well-known issue of error 0x5D when booting Win 7 x64 on qemu without kvm, marked as resolved at Linux.

Used qemu for Windows downloaded from http://qemu.weilnetz.de/
Tested on  qemu 2.3.94 64-bit and  qemu 2.4.0 32-bit.

Options :
qemu-system-x86_64.exe  -m 1536 -cpu qemu64,+nx,+pae,+mce,+cx8,+apic,+sep,+mtrr,+pge,+mca,+cmov,+pat,+pse36,+clflush,+acpi,+mmx,+fxsr,+sse,+sse2,+ss,+fxsr,+sse,+sse2,+ss,+de,+mtrr,+mca,+clflush
 win_7_work.qcow2

On qemu at Ubuntu with kvm Win7 x64 works ,but mouse is unusable as mentioned above.

A solution is to convert from vmdk to qcow2 and back working in VmWare with Windows images. Repeated  Windows activation could be needed.

Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Have you tried "-usb -device usb-tablet" already?


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