summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/118/none/1563931
blob: 28995a4db589411d65f3e360f926e12141adb789 (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
device: 0.629
graphic: 0.576
socket: 0.547
semantic: 0.477
assembly: 0.475
kernel: 0.436
mistranslation: 0.423
files: 0.416
x86: 0.409
permissions: 0.398
user-level: 0.390
architecture: 0.361
i386: 0.358
boot: 0.358
network: 0.357
hypervisor: 0.328
register: 0.328
risc-v: 0.321
vnc: 0.312
peripherals: 0.311
performance: 0.306
VMM: 0.304
ppc: 0.286
debug: 0.264
TCG: 0.264
arm: 0.249
PID: 0.246
virtual: 0.228
KVM: 0.222

qemu-img should allow resizing image with snapshots

Currently it's not possible to resize a disk image with qemu-img if image in question has snapshots associated. I'm not entirely sure this is technically possible but if it is, it would be really nice to support that.

$ qemu-img --version
qemu-img version 2.4.1 (qemu-2.4.1-8.fc23), Copyright (c) 2004-2008 Fabrice Bellard

The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.

If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.

Thank you and sorry for the inconvenience.


Implemented in 7fa140abf69675b7b83af32de.  Note that every internal snapshot has a disk size associated with it, though, so applying a snapshot from when the image had a different size means the image size will be reverted to what it was as the time of the snapshot.