1 files changed, 55 insertions, 0 deletions
diff --git a/results/classifier/118/none/1652459 b/results/classifier/118/none/1652459
new file mode 100644
index 000000000..b60824740
--- /dev/null
+++ b/results/classifier/118/none/1652459
@@ -0,0 +1,55 @@
+device: 0.689
+KVM: 0.656
+kernel: 0.631
+architecture: 0.575
+register: 0.574
+network: 0.568
+mistranslation: 0.559
+hypervisor: 0.545
+ppc: 0.527
+peripherals: 0.522
+semantic: 0.519
+virtual: 0.505
+performance: 0.491
+PID: 0.481
+vnc: 0.479
+files: 0.474
+graphic: 0.455
+socket: 0.436
+debug: 0.435
+i386: 0.426
+x86: 0.418
+permissions: 0.378
+user-level: 0.346
+VMM: 0.328
+TCG: 0.320
+risc-v: 0.317
+boot: 0.297
+arm: 0.269
+assembly: 0.248
+
+kvm rbd driver (and maybe others, i.e. qcow2, qed and so on)  does not report DISCARD-ZERO flag
+
+# lsblk -D
+NAME   DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO
+sda           0        4K       1G         0
+├─sda1        0        4K       1G         0
+├─sda2     1024        4K       1G         0
+└─sda5        0        4K       1G         0
+
+
+Last column should be `1` at least for "RBD+discard=unmap" since reading from discarded regions in RBD MUST return zeroes. The same with QCOW2, QED and sparse raw images. KVM should copy value of this flag when real raw device (i.e. real SSD) with discard capability is used as virtual disk.
+
+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 all 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". Thank you and sorry for the inconvenience.
+
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/139
+
+