1 files changed, 77 insertions, 0 deletions
diff --git a/results/classifier/118/none/1912107 b/results/classifier/118/none/1912107
new file mode 100644
index 000000000..53a87b891
--- /dev/null
+++ b/results/classifier/118/none/1912107
@@ -0,0 +1,77 @@
+x86: 0.772
+architecture: 0.734
+user-level: 0.636
+graphic: 0.612
+semantic: 0.606
+kernel: 0.566
+performance: 0.554
+permissions: 0.549
+device: 0.506
+mistranslation: 0.472
+register: 0.454
+files: 0.431
+network: 0.430
+socket: 0.406
+hypervisor: 0.405
+ppc: 0.397
+peripherals: 0.385
+debug: 0.384
+vnc: 0.349
+PID: 0.344
+boot: 0.335
+TCG: 0.330
+arm: 0.330
+risc-v: 0.310
+VMM: 0.291
+assembly: 0.233
+KVM: 0.222
+virtual: 0.160
+i386: 0.057
+
+Option to constrain linux-user exec() to emulated CPU only
+
+When trying to reproduce a bug someone reported on an actual AMD K10[1], I tried to directly throw `qemu_x86-64 -cpu 
+phenom path/to/wrongly-labelled-instruction-set/gcc 1.c` at the problem, but failed to get an "illegal instruction" as expected. A quick investigation reveals that the error is actually caused by one of gcc's child processess, and that the said process is being ran directly on the host. A similar problem happens with trying to call stuff with /usr/bin/env.
+
+ [1]: https://github.com/Homebrew/brew/issues/1034
+
+Since both the host and the guest are x86_64, I deemed binfmt inapplicable to my case. I believe that QEMU should offer a way to modify exec() and other spawning syscalls so that execution remains on an emulated CPU in such a case. Call it an extra layer of binfmt, if you must.
+
+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.
+
+
+
+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/306
+
+