From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] i386-linux-user on ARM host
Date: Wed, 9 Sep 2009 10:46:16 +0200 [thread overview]
Message-ID: <761ea48b0909090146y447da167o4ad5258d12a6eb80@mail.gmail.com> (raw)
In-Reply-To: <4AA6F0F2.2050409@mlbassoc.com>
On Wed, Sep 9, 2009 at 2:04 AM, Gary Thomas<gary@mlbassoc.com> wrote:
[...]
>
> Sorry all, I've now figured out that it _does_ work, just not
> like I expected. It seems that without a -L option to qemu,
> the executed code runs in something like a 'chroot' jail. Is
> this the case? If so, is there any way to let the emulated
> program live in the same file system [space] as other applications?
>
> The idea would be to be able to execute some program, e.g. something
> available as x86 only, on the ARM target and make the process as
> invisible as possible. Can this be made to work?
How would you handle shared libraries?
Laurent
prev parent reply other threads:[~2009-09-09 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 18:24 [Qemu-devel] i386-linux-user on ARM host Gary Thomas
2009-09-08 21:35 ` Gary Thomas
2009-09-09 0:04 ` Gary Thomas
2009-09-09 8:46 ` Laurent Desnogues [this message]
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=761ea48b0909090146y447da167o4ad5258d12a6eb80@mail.gmail.com \
--to=laurent.desnogues@gmail.com \
--cc=gary@mlbassoc.com \
--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).