other: 0.192
semantic: 0.130
device: 0.111
KVM: 0.086
PID: 0.072
graphic: 0.053
debug: 0.052
files: 0.051
network: 0.051
vnc: 0.050
performance: 0.047
permissions: 0.043
socket: 0.035
boot: 0.028
KVM: 0.626
debug: 0.071
other: 0.059
device: 0.056
files: 0.056
semantic: 0.024
performance: 0.024
PID: 0.016
network: 0.015
boot: 0.013
socket: 0.011
permissions: 0.011
graphic: 0.009
vnc: 0.008

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