From: Warner Losh <imp@bsdimp.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Mauricio Galindo <up.mauricio.g@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU user mode execve
Date: Thu, 3 Oct 2019 13:41:03 -0600 [thread overview]
Message-ID: <CANCZdfrSNmnsW4YDRV3GYD9FCv+kjmB_Wos44ieiUQFGwNdk6Q@mail.gmail.com> (raw)
In-Reply-To: <20191003193255.GJ17916@kitsune.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On Thu, Oct 3, 2019 at 1:36 PM Michal Suchánek <msuchanek@suse.de> wrote:
> On Thu, Oct 03, 2019 at 10:48:46AM -0700, Mauricio Galindo wrote:
> > Hi,
> >
> > I'm running QEMU in user mode and I'm running into issues when trying
> > to exec binaries within the emulated process given that binaries are
> > expected to run in the native architecture. Would it be useful to have
> > an option to rewrite execve(/bin/some_binary, ...) to
> > execve(qemu-$arch-static, [/bin/some_binary, ...], ...)?
> >
>
> This is handled in kernel by binfmt-misc.
>
> Debian has nice packaging for the required configuration. They use it to
> create non-native installation images.
>
FreeBSD also uses bsd-user (admittedly a much changed one from what's
upstream[*]) to build non-native packages. It uses the same binfmt stuff in
a chroot.
Warner
[*] I've rebased our work forward up through 3.1 release and hope to have
it rebased through the top of the tree shortly and have it ready for
upstreaming soon.
[-- Attachment #2: Type: text/html, Size: 1452 bytes --]
next prev parent reply other threads:[~2019-10-03 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 17:48 QEMU user mode execve Mauricio Galindo
2019-10-03 19:32 ` Michal Suchánek
2019-10-03 19:41 ` Warner Losh [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-03 16:12 Mauricio Galindo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANCZdfrSNmnsW4YDRV3GYD9FCv+kjmB_Wos44ieiUQFGwNdk6Q@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=msuchanek@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=up.mauricio.g@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).