blob: 6f37a4307b0cc89e0eeb5203038823f2956e33b2 (
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
65
66
67
68
|
boot: 0.579
graphic: 0.565
device: 0.387
performance: 0.382
i386: 0.260
ppc: 0.245
PID: 0.200
semantic: 0.199
register: 0.196
socket: 0.174
permissions: 0.160
user-level: 0.145
architecture: 0.132
files: 0.122
vnc: 0.118
x86: 0.113
network: 0.111
mistranslation: 0.111
risc-v: 0.109
hypervisor: 0.103
debug: 0.101
TCG: 0.063
arm: 0.060
peripherals: 0.060
kernel: 0.058
VMM: 0.053
virtual: 0.051
assembly: 0.026
KVM: 0.018
Recent regression: segfault on startup with -snapshot
As of git revision 041ccc922ee474693a2869d4e3b59e920c739bc0, qemu segfaults on startup when I try to boot a hard disk image with the -snapshot option.
To reproduce:
wget http://wiki.qemu.org/download/linux-0.2.img.bz2
bunzip2 linux-0.2.img.bz2
qemu-system-i386 -hda linux-0.2.img -snapshot
When I run this, qemu-system-i386 crashes with a segmentation fault. This is on a Debian 7 amd64 host.
git bisect implicates the following commit:
commit a464982499b2f637f6699e3d03e0a9d2e0b5288b
Author: Paolo Bonzini <email address hidden>
Date: Wed Feb 11 17:15:18 2015 +0100
rcu: run RCU callbacks under the BQL
This needs to go away sooner or later, but one complication is the
complex VFIO data structures that are modified in instance_finalize.
Take a shortcut for now.
Reviewed-by: Michael Roth <email address hidden>
Tested-by: Michael Roth <email address hidden>
Signed-off-by: Paolo Bonzini <email address hidden>
I believe this was resolved in:
commit 6b49809c597331803ea941eadda813e5bb4e8fe2
Author: Paolo Bonzini <email address hidden>
Date: Fri Feb 27 19:58:23 2015 +0100
cpus: fix deadlock and segfault in qemu_mutex_lock_iothread
The problem cannot be reproduced in qemu.git/master (fc85cf4a8199a657fdfd5fb902f1835973406454).
|