blob: 3e2dd6cee515bd60b4945bc1fa7afdffd28d8228 (
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
|
graphic: 0.621
performance: 0.601
semantic: 0.564
device: 0.550
kernel: 0.547
boot: 0.480
architecture: 0.412
debug: 0.386
i386: 0.382
ppc: 0.382
user-level: 0.357
virtual: 0.355
network: 0.352
vnc: 0.351
hypervisor: 0.350
x86: 0.340
permissions: 0.315
socket: 0.289
mistranslation: 0.280
PID: 0.248
register: 0.224
peripherals: 0.221
assembly: 0.195
VMM: 0.169
files: 0.154
KVM: 0.129
risc-v: 0.104
arm: 0.104
TCG: 0.077
qemu-system-mipsel save/restore broken
Save and restore on mipsel seems to be broken (tested with commit 1c97e303d4ea80a2691334b0febe87a50660f99d). To reproduce:
1. Download debian_squeeze_mipsel_standard.qcow2 and vmlinux-2.6.32-5-4kc-malta from from http://people.debian.org/~aurel32/qemu/mipsel/
2. Boot the system. I had to ^D past a Bus error in fsck, which may be another bug (haven't investigated). The command line used was:
qemu-system-mipsel -M malta -kernel vmlinux-2.6.32-5-4kc-malta -hda debian_squeeze_mipsel_standard.qcow2 -append "root=/dev/sda1 console=tty0" -k en-us -vnc :0
3. Once the system is booted, go to the monitor and do "savevm booted". Then quit.
4. Re-run qemu-system-mipsel again with "-loadvm booted". The guest system comes back but is hung (the monitor remains responsive, however).
I also captured a debug log, which is attached. The immediate cause of the freeze seems to be that it's stuck in a loop repeatedly handling the same page fault over and over.
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.]
|