blob: 92579a1b921a9b38557a9b5924af2eb560609593 (
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
|
graphic: 0.989
architecture: 0.967
semantic: 0.960
device: 0.875
performance: 0.858
x86: 0.856
vnc: 0.829
arm: 0.760
files: 0.703
ppc: 0.674
VMM: 0.672
debug: 0.669
register: 0.642
assembly: 0.641
virtual: 0.600
PID: 0.586
permissions: 0.581
user-level: 0.580
kernel: 0.579
peripherals: 0.573
socket: 0.556
i386: 0.549
risc-v: 0.499
hypervisor: 0.479
network: 0.446
TCG: 0.351
boot: 0.332
mistranslation: 0.325
KVM: 0.260
Segfault when saving VM snapshot via QEMU monitor on MIPS and MIPSEL
Description of problem:
When entering the QEMU monitor using Ctrl-A then C, and running the savevm QEMU command, the emulator hangs for a while and then exits with a segfault. This occurs on MIPS and MIPSEL system emulators using the same command line arguments. ARM32, aarch64 and x86_64 emulators don't seem to have this problem. I haven't tested it on any other architectures as I don't have kernel or drive images for them. `qemu-img` seems to work fine with the QCOW2 images used for this test, I was able to create and load offline snapshots from them. The images were created from raw EXT2 filesystem images produced by Buildroot, using `qemu-img convert`.
Steps to reproduce:
1. Start the QEMU system emulator for MIPS/MIPSEL with the given command line.
2. Enter the QEMU monitor with Ctrl-A, C.
3. Run `savevm <vm name>`.
Additional information:
I tried logging what QEMU was doing with the `-D ./log.txt` command line option, but the produced log file was empty.
If you need me to send you the kernel image files and QCOW2 images used, I would be happy to do so.
|