1 files changed, 52 insertions, 0 deletions
diff --git a/results/classifier/118/none/1563931 b/results/classifier/118/none/1563931
new file mode 100644
index 000000000..28995a4db
--- /dev/null
+++ b/results/classifier/118/none/1563931
@@ -0,0 +1,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.
+