blob: d932e52286f8baddc28885790aa1e6fd9a9cbab6 (
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
|
kernel: 0.881
boot: 0.822
x86: 0.818
device: 0.798
VMM: 0.741
architecture: 0.739
graphic: 0.675
virtual: 0.668
semantic: 0.642
network: 0.567
PID: 0.559
permissions: 0.472
vnc: 0.419
performance: 0.401
ppc: 0.398
i386: 0.370
register: 0.346
arm: 0.325
debug: 0.319
risc-v: 0.298
files: 0.260
TCG: 0.255
socket: 0.240
hypervisor: 0.217
mistranslation: 0.202
peripherals: 0.160
user-level: 0.150
KVM: 0.128
assembly: 0.060
qemu 6.2 memory leak when failed to boot and infinitely reboot
Description of problem:
qemu allocates tons of memory (very likely memory leak) in certain (rare) cases.
When I misconfigured qemu so that I have run a bigger linux kernel within insufficient memory (for example 8M bzImage while 16M ram and no hdd), the kernel will obviously fail to boot. In this case qemu will reboot (likely the linux kernel reboots). However reboot does not solve the problem, causing qemu to repeatedly reboot.
Memory usage of qemu raises sharply in the progress.
Steps to reproduce:
1. Get any linux kernel (tested with 5.15.33)
2. Run the kernel on qemu, with memory smaller than necessary
Additional information:
A reproducing dockerfile:
```
FROM alpine:3.15
RUN apk add qemu-system-x86_64 linux-virt
CMD ["/usr/bin/qemu-system-x86_64", "-kernel", "/boot/vmlinuz-virt", "-nographic", "-net", "none", "-m", "16M"]
```
|