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
|
device: 0.493
x86: 0.484
kernel: 0.409
hypervisor: 0.354
performance: 0.339
architecture: 0.318
socket: 0.305
ppc: 0.274
user-level: 0.262
graphic: 0.237
semantic: 0.230
boot: 0.216
virtual: 0.209
vnc: 0.202
PID: 0.198
mistranslation: 0.179
network: 0.171
register: 0.170
peripherals: 0.161
files: 0.152
KVM: 0.134
i386: 0.108
debug: 0.107
risc-v: 0.107
VMM: 0.084
permissions: 0.082
arm: 0.076
assembly: 0.064
TCG: 0.059
qemu Windows 7 BSOD when using hv-time
When I use hv-time sub option and run CPU-Z or 3DMark (Physics Test) the Windiws 7 guest stops with BSOD (SYSTEM_SERVICE_EXCEPTION). It can be easily reproduced by running CPU-Z. It will fail every second or third time you execute CPU-Z and fail during "PCI detection". If I disable hv-time I can run CPU-Z and 3DMark (Physics Test) without any problems. QEMU was called with the following options:
/usr/bin/taskset -c 4,5,6,7 /usr/bin/qemu-system-x86_64 \
-machine q35,accel=kvm,kernel_irqchip=on \
-enable-kvm \
-serial none \
-parallel none \
-monitor none \
-vga std \
-boot order=dc \
-cpu host,hv-time \
-smp cores=4,threads=1,sockets=1 \
-m 8192 \
-k de \
-rtc base=localtime \
-drive file=/srv/kvm/maggie-drive0.img,id=drive0,if=none,cache=none,aio=threads \
-mon chardev=monitor0 \
-chardev socket,id=monitor0,path=/tmp/maggie.monitor,nowait,server \
-netdev tap,id=net0,vhost=on,helper=/usr/lib/qemu/qemu-bridge-helper \
-device virtio-net-pci,netdev=net0,mac=00:00:00:02:01:01 \
-device virtio-blk-pci,drive=drive0,ioeventfd=on \
-device ioh3420,bus=pcie.0,id=pcie0,port=1,chassis=1,multifunction=on
I've removed the VFIO PCI passthrough line of my GPU to make reproduction easier. In any case it happens in both scenarios so VGA passthrough is not the root cause. It happens with linux-3.15-rc5 and linux-3.14.3 with patch from commit mentioned at https://bugzilla.kernel.org/show_bug.cgi?id=73721#c3
Forgot to mention. Used qemu version was 2.0.0.
Triaging old bug tickets ... can you still reproduce this issue with the
latest version of QEMU?
[Expired for QEMU because there has been no activity for 60 days.]
|