blob: 2bbfc30a631db85540243dcbe811e50998641d2d (
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
|
device: 0.789
graphic: 0.734
performance: 0.709
files: 0.682
PID: 0.570
semantic: 0.462
other: 0.388
permissions: 0.324
socket: 0.294
debug: 0.283
network: 0.264
vnc: 0.212
boot: 0.111
KVM: 0.060
vmdk files cause qemu-img to consume lots of time and memory
The two attached files cause 'qemu-img info' to consume lots of time and memory. Around 10-12 seconds of CPU time, and around 3-4 GB of heap.
$ /usr/bin/time ~/d/qemu/qemu-img info afl10.img
qemu-img: Can't get size of device 'image': File too large
0.40user 11.57system 0:12.03elapsed 99%CPU (0avgtext+0avgdata 4197804maxresident)k
56inputs+0outputs (0major+1045672minor)pagefaults 0swaps
$ /usr/bin/time ~/d/qemu/qemu-img info afl11.img
image: afl11.img
file format: vmdk
virtual size: 12802T (14075741666803712 bytes)
disk size: 4.0K
cluster_size: 65536
Format specific information:
cid: 4294967295
parent cid: 4294967295
create type: monolithicSparse
extents:
[0]:
virtual size: 14075741666803712
filename: afl11.img
cluster size: 65536
format:
0.29user 9.10system 0:09.43elapsed 99%CPU (0avgtext+0avgdata 3297360maxresident)k
8inputs+0outputs (0major+820507minor)pagefaults 0swaps
Both files were found by using american-fuzzy-lop.
Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
[Expired for QEMU because there has been no activity for 60 days.]
|