[Bug 1912107] Re: Option to constrain linux-user exec() to emulated CPU only

[Thomas Huth]

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


** Changed in: qemu
       Status: New => Expired

** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #306
   https://gitlab.com/qemu-project/qemu/-/issues/306

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1912107

Title:
  Option to constrain linux-user exec() to emulated CPU only

Status in QEMU:
  Expired

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1912107/+subscriptions