1 files changed, 0 insertions, 43 deletions
diff --git a/results/classifier/118/performance/1784 b/results/classifier/118/performance/1784
deleted file mode 100644
index 188ea400a..000000000
--- a/results/classifier/118/performance/1784
+++ /dev/null
@@ -1,43 +0,0 @@
-performance: 0.955
-device: 0.921
-graphic: 0.911
-permissions: 0.808
-assembly: 0.805
-peripherals: 0.785
-files: 0.771
-semantic: 0.757
-mistranslation: 0.705
-network: 0.695
-register: 0.695
-boot: 0.679
-user-level: 0.654
-architecture: 0.643
-debug: 0.637
-vnc: 0.633
-socket: 0.606
-PID: 0.577
-kernel: 0.513
-arm: 0.489
-risc-v: 0.473
-ppc: 0.420
-i386: 0.420
-hypervisor: 0.413
-x86: 0.392
-VMM: 0.389
-TCG: 0.344
-virtual: 0.336
-KVM: 0.206
-
-Mac M1 Max / Debian guest / Luks password / Switching to graphical login manager (lightdm/Gdm) hangs in 75%
-Description of problem:
-In approximately 70% of cases I start QEMU with a Debian guest where the Debian guest was installed with full disk encryption, QEMU 'hangs' (does not respond') after I unlock the encrypted guest and the guest tries to start the graphical login manager (gdm or lightdm).
-
-I need to force quit QEMU, restart it multiple times until the start of the graphical login manager works.
-Steps to reproduce:
-1. Install Debian with (guided) full disk encryption and either the Gnome or the XFCE desktop environment
-2. To be able to unlock the hard disk after the installation finished, the Linux boot parameter 'console=tty1' needs to be added within grub to the Linux command line
-3. Try to restart/reboot QEMU  several times and QEMU will become unresponsive multiple times in this process.
-Additional information:
-I encounter this problem for several months now, with different versions of QEMU, macOS and Debian.
-
-There is one observation, which might help: I installed [DropBear](https://packages.debian.org/buster/dropbear-initramfs) to experiment with remote unlocking of Luks encrypted Linux boxes. It seems, that QEMU does not go into the unresponsive state, when I unlock the hard disk via SSH and not focus the QEMU window until after the graphical login manager started. (Only tried remote unlocking a few times so it is too early to confirm if this works 100% of the time.