blob: 2acc7bac0dd81c5a011827f6d060a10dbc266785 (
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
|
graphic: 0.903
device: 0.857
semantic: 0.732
other: 0.721
vnc: 0.710
network: 0.677
instruction: 0.637
mistranslation: 0.580
socket: 0.517
boot: 0.447
assembly: 0.282
KVM: 0.019
RFE: More info in qemu-img info/check
Originally filed in Fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=861375
"""
qemu-img info currently give me info like this:
image: /home/alex/.local/share/gnome-boxes/images/Fedora 16
file format: qcow2
virtual size: 11G (11794287616 bytes)
disk size: 4.5G
cluster_size: 65536
In order to figure out the "health" of an image there is some more information I would like:
in-use disk size - I.e the subset of disk size that is not marked as unused due to e.g. TRIM operations
amount of compressed clusters. I.e. "is it useful to re-compress the image".
Fragmentation estimation.
This would be useful to both sysadmins in general and for automated things like
what we want to do in gnome-boxes:
https://bugzilla.gnome.org/show_bug.cgi?id=685032
"""
As mentioned in the original report, qemu-img check currently has fragmentation stats, but only for QED.
qemu-img check has reported allocated clusters, compressed clusters and fragmentation for qcow2 images since February 2013 (QEMU 1.5).
|