1 files changed, 43 insertions, 0 deletions
diff --git a/results/classifier/118/virtual/1314293 b/results/classifier/118/virtual/1314293
new file mode 100644
index 000000000..49f6777ae
--- /dev/null
+++ b/results/classifier/118/virtual/1314293
@@ -0,0 +1,43 @@
+virtual: 0.847
+VMM: 0.806
+device: 0.786
+graphic: 0.728
+performance: 0.710
+network: 0.658
+semantic: 0.632
+mistranslation: 0.584
+architecture: 0.520
+vnc: 0.514
+risc-v: 0.509
+kernel: 0.507
+socket: 0.489
+debug: 0.472
+PID: 0.462
+i386: 0.458
+ppc: 0.452
+TCG: 0.434
+KVM: 0.431
+register: 0.429
+hypervisor: 0.425
+boot: 0.391
+x86: 0.371
+files: 0.352
+user-level: 0.320
+permissions: 0.276
+peripherals: 0.271
+arm: 0.270
+assembly: 0.266
+
+screendump with qxl + spice shows stale data
+
+The monitor 'screendump' command returns stale data for VMs using qxl + spice. If you perform multiple screendumps, screendump #N will show roughly the display from the time screendump #N-1 was taken. This affects 'virsh screenshot' and libvirt screenshot APIs by association.
+
+Gerd explains that new monitor commands/infrastructure is likely required to handle this correctly:
+
+https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg03840.html
+
+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.]
+