1 files changed, 38 insertions, 0 deletions
diff --git a/results/classifier/105/boot/1756538 b/results/classifier/105/boot/1756538
new file mode 100644
index 000000000..474397dc1
--- /dev/null
+++ b/results/classifier/105/boot/1756538
@@ -0,0 +1,38 @@
+boot: 0.871
+other: 0.858
+graphic: 0.855
+device: 0.841
+semantic: 0.827
+KVM: 0.737
+instruction: 0.733
+mistranslation: 0.655
+network: 0.473
+assembly: 0.461
+vnc: 0.447
+socket: 0.421
+
+Minimal Ubuntu vs. Debian differences
+
+I'm using Qemu on Ubuntu (minimal) and Debian (minimal) on Android (Arch64) via Linux Deploy to run Windows guests. Here's a few issues I encountered:
+
+1) Qemu on (minimal) Debian 9 and Ubuntu cannot run Windows 7-10 guests (only Windows XP and below) because there's a black screen after the boot menu. Qemu on Debian 10, however, can run Windows 7. Incidentally, these distros run on the host in bios compatibility mode instead of UEFI. Ubuntu Desktop (full distro) on other hosts does not display the black screen when running Qemu.
+
+2) Qemu on Debian 9-10 (minimal) does not display fullscreen - but Ubuntu minimal does display full-screen.
+
+3) Qemu on Limbo PC Emulator and on Debian 9-10 only run windows guests at 1 GHz using the default Qemu CPU, but Ubuntu runs windows guests at 2 GHz using the default Qemu CPU.
+
+4) Enable KVM doesn't work, and virtualization isn't detected through Limbo PC Emulator and minimal Linux distros running on Android - perhaps is a problem with running Linux distros via Linux Deploy using Chroot on Android (not so much a Qemu-KVM issue) and failing to detect ARMv8-A CPUs that are indeed capable of virtualization.
+
+Can anyone explain these differences? I believe they are all using the latest versions of Qemu.
+
+One more: Qemu on Debian 9-10 minimal requires -show cursor command to use the mouse inside a windows guest, but with Qemu on Ubuntu minimal the cursor is controllable by default. Again, this is all within the context of an Android/Arm8/Linux minimal/Chroot-based host. 
+
+Qemu Virtual CPU is capping at 1 GHz for version 2.5+ and 2 GHz for version 2.4
+
+I tested qemu32 and qemu64. This is strange because my ARMv8-a CPU is 2.4 GHz. 
+
+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 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". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+