2 files changed, 79 insertions, 0 deletions
diff --git a/results/classifier/118/none/726 b/results/classifier/118/none/726
new file mode 100644
index 00000000..5382c45a
--- /dev/null
+++ b/results/classifier/118/none/726
@@ -0,0 +1,31 @@
+kernel: 0.746
+device: 0.729
+network: 0.665
+files: 0.663
+mistranslation: 0.595
+arm: 0.595
+socket: 0.566
+semantic: 0.531
+vnc: 0.511
+ppc: 0.507
+performance: 0.487
+graphic: 0.482
+permissions: 0.473
+VMM: 0.471
+register: 0.461
+architecture: 0.448
+assembly: 0.433
+peripherals: 0.410
+PID: 0.393
+TCG: 0.364
+debug: 0.353
+risc-v: 0.327
+hypervisor: 0.321
+boot: 0.299
+KVM: 0.287
+user-level: 0.253
+virtual: 0.230
+x86: 0.147
+i386: 0.107
+
+Missing 6.2.0-rc0 tarball on https://download.qemu.org/
diff --git a/results/classifier/118/none/726619 b/results/classifier/118/none/726619
new file mode 100644
index 00000000..e144318d
--- /dev/null
+++ b/results/classifier/118/none/726619
@@ -0,0 +1,48 @@
+performance: 0.699
+graphic: 0.698
+device: 0.677
+architecture: 0.580
+semantic: 0.567
+network: 0.563
+PID: 0.488
+vnc: 0.471
+ppc: 0.432
+i386: 0.431
+files: 0.431
+mistranslation: 0.429
+socket: 0.400
+x86: 0.382
+permissions: 0.343
+hypervisor: 0.335
+register: 0.333
+risc-v: 0.327
+VMM: 0.291
+debug: 0.287
+kernel: 0.287
+user-level: 0.260
+virtual: 0.258
+boot: 0.240
+peripherals: 0.217
+assembly: 0.186
+TCG: 0.175
+arm: 0.174
+KVM: 0.095
+
+loadvm does not load (offline) snapshot anymore
+
+qemu Version: 0.14.0
+The problem is present in the current code from git master as well.
+
+Loading a snapshot that was created while qemu was not running (using qemu-img) does not seem to work anymore.
+
+Using "loadvm <snapshot-id>" in the qemu monitor does not have the desired effect. Not even an error message is displayed.
+
+I was able to track down the problem (using git bisect) to this commit:
+http://git.qemu.org/qemu.git/commit/?id=f0aa7a8b2d518c54430e4382309281b93e51981a
+
+After reverting that commit in my local git checkout everything is workin as expected again.
+
+Triaging old bug tickets ... can you somehow still reproduce this problem with the latest version of QEMU (currently v2.9), or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+