1 files changed, 68 insertions, 0 deletions
diff --git a/results/classifier/105/other/1914294 b/results/classifier/105/other/1914294
new file mode 100644
index 00000000..d000e6f5
--- /dev/null
+++ b/results/classifier/105/other/1914294
@@ -0,0 +1,68 @@
+other: 0.861
+graphic: 0.808
+device: 0.718
+instruction: 0.717
+mistranslation: 0.697
+semantic: 0.615
+network: 0.583
+vnc: 0.570
+socket: 0.537
+KVM: 0.534
+assembly: 0.529
+boot: 0.501
+
+Windows XP displays black screen when smp option is used
+
+When I use Windows XP with the -smp option, the screen goes black. The only thing I can see is a cursor. I have tried -smp 2, -smp cores=4, and -smp cores=2.
+
+My info:
+
+Host:
+M1 Mac
+Mac OS 11.1
+QEMU 5.2 at cf7ca7d5b9faca13f1f8e3ea92cfb2f741eb0c0e.
+
+Guest:
+32-bit Windows XP SP3 build 2600.
+
+Command line to reproduce this issue: 
+qemu-system-i386 -m 700 -hda <Windows XP HD image file> -smp 2
+
+Last commit tested with this problem: 1214d55d1c41fbab3a9973a05085b8760647e411
+
+I restarted QEMU without the '-smp 2' option and Windows XP started working again. The only problem is the host CPU usage will stay at 100% even with the guest CPU load being close to 0%. The only way to fix this problem that I know currently is to reinstall Windows XP. 
+
+To fix this problem open Windows XP's System Restore and restore from a point before using the smp option.
+
+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.]
+