From: Riku Voipio <riku.voipio@iki.fi>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: peter.maydell@linaro.org, Riku Voipio <riku.voipio@iki.fi>,
Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user: enabling binfmt P flag
Date: Mon, 25 Aug 2014 17:49:17 +0300 [thread overview]
Message-ID: <20140825144917.GA17919@afflict.kos.to> (raw)
In-Reply-To: <OFC5EFA22A.22F00923-ONC1257D3F.004F2F99-C1257D3F.004FB69B@transmode.se>
On Mon, Aug 25, 2014 at 04:30:40PM +0200, Joakim Tjernlund wrote:
> Riku Voipio <riku.voipio@iki.fi> wrote on 2014/08/25 15:55:55:
> >
> > Hi,
> >
> > On Mon, Aug 25, 2014 at 03:39:19PM +0200, Joakim Tjernlund wrote:
> > > Then consider when you run a LXC without P flag.
> >
> > Please remember that your usecase of running Qemu in LXC is a new
> feature,
> > never before supported. Adding new features is always nice. However, it
> must
> > not happen with expense of regressing already working features
> > (traditional chroot).
> OK, but traditional chroot is unaffected with my patch. Only binfmt
> users which uses the binfmt flag O will have to change to PO. How
> many is that?
Traditional chroot is with binfmt_misc. Debian and ubuntu packages of
Qemu enable OC flags, so at least all debian/ubuntu users who use qemu
linux-user in chroots are affected.
Using OC seems quite typical:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-emulation/qemu/files/qemu-binfmt.initd-r1?view=markup
http://rwmj.wordpress.com/2013/12/22/how-to-run-aarch64-binaries-on-an-x86-64-host-using-qemu-userspace-emulation/#content
Others, like Suse, scratchbox use the P flag and wrapper binary.
next prev parent reply other threads:[~2014-08-25 14:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 9:09 [Qemu-devel] linux-user: enabling binfmt P flag Riku Voipio
2014-08-25 9:14 ` Alexander Graf
2014-08-25 11:10 ` Joakim Tjernlund
2014-08-25 12:42 ` Riku Voipio
2014-08-25 12:46 ` Alexander Graf
2014-08-25 13:18 ` Riku Voipio
2014-08-25 13:20 ` Laurent Vivier
2014-08-25 13:39 ` Joakim Tjernlund
2014-08-25 13:55 ` Riku Voipio
2014-08-25 14:30 ` Joakim Tjernlund
2014-08-25 14:49 ` Riku Voipio [this message]
2014-08-25 15:02 ` Joakim Tjernlund
[not found] ` <OF93B0417A.866825C3-ONC1257D3F.005235F4-C1257D3F.0052A534@LocalDomain>
2014-08-28 16:06 ` Joakim Tjernlund
2014-08-29 18:01 ` Peter Maydell
2014-08-30 8:28 ` Joakim Tjernlund
2014-09-01 8:51 ` Paolo Bonzini
2014-09-01 9:12 ` Peter Maydell
2014-09-01 9:28 ` Paolo Bonzini
2014-09-01 9:32 ` Peter Maydell
2014-09-01 9:51 ` Riku Voipio
2014-09-17 15:34 ` Joakim Tjernlund
2014-09-17 16:12 ` Peter Maydell
2014-09-17 19:25 ` Paolo Bonzini
2014-09-17 19:31 ` Peter Maydell
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=20140825144917.GA17919@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=agraf@suse.de \
--cc=joakim.tjernlund@transmode.se \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).