1 files changed, 68 insertions, 0 deletions
diff --git a/results/classifier/118/device/1925094 b/results/classifier/118/device/1925094
new file mode 100644
index 000000000..47d136e64
--- /dev/null
+++ b/results/classifier/118/device/1925094
@@ -0,0 +1,68 @@
+device: 0.827
+virtual: 0.777
+graphic: 0.679
+user-level: 0.636
+semantic: 0.609
+architecture: 0.579
+hypervisor: 0.572
+network: 0.571
+ppc: 0.570
+performance: 0.549
+KVM: 0.525
+vnc: 0.517
+TCG: 0.512
+debug: 0.509
+risc-v: 0.508
+mistranslation: 0.508
+PID: 0.505
+permissions: 0.498
+files: 0.498
+VMM: 0.485
+peripherals: 0.469
+register: 0.459
+socket: 0.430
+i386: 0.394
+x86: 0.369
+kernel: 0.363
+boot: 0.355
+arm: 0.315
+assembly: 0.301
+
+DISCARD support for Crypto Block Devices
+
+It appears that running `fstrim` or similar is useless when the VM is on a LUKS-encrypted device using QEMU's native LUKS support.
+
+Looking at the source, it seems that block/crypto.c lacks an implementation for bdrv_co_pdiscard, which probably needs to delegate to a per-crypto type discard helper.
+
+The QEMU project is currently moving 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 the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" or "Confirmed" within the next 60 days (other-
+wise it will get closed as "Expired"). We will then eventually migrate
+the ticket automatically to the new system (but you won't be the reporter
+of the bug in the new system and thus you won't get notified on changes
+anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+