All raised issues fixed, I just sent v2 :)
On Fri, Jan 22, 2016 at 3:00 AM, Laurent Vivier wrote:
>
>
> Le 22/01/2016 11:47, Peter Maydell a écrit :
>> On 22 January 2016 at 10:33, Laurent Vivier wrote:
>>> Le 22/01/2016 11:01, Petros Angelatos a écrit :
On 22 January 2016 at 10:33, Laurent Vivier wrote:
> Le 22/01/2016 11:01, Petros Angelatos a écrit :
>> This was my initial approach too, but argv[0] can be just the filename
>> like "qemu-arm-static". And while I could add extra logic to look this
>> up in the PATH, someone
>> diff --git a/linux-user/main.c b/linux-user/main.c
>> index ee12035..5951279 100644
>> --- a/linux-user/main.c
>> +++ b/linux-user/main.c
>> @@ -79,6 +79,7 @@ static void usage(int exitcode);
>>
>> static const char *interp_prefix = CONFIG_QEMU_INTERP_PREFIX;
>> const char
Le 22/01/2016 11:01, Petros Angelatos a écrit :
>>> diff --git a/linux-user/main.c b/linux-user/main.c
>>> index ee12035..5951279 100644
>>> --- a/linux-user/main.c
>>> +++ b/linux-user/main.c
>>> @@ -79,6 +79,7 @@ static void usage(int exitcode);
>>>
>>> static const char *interp_prefix =
Le 22/01/2016 11:47, Peter Maydell a écrit :
> On 22 January 2016 at 10:33, Laurent Vivier wrote:
>> Le 22/01/2016 11:01, Petros Angelatos a écrit :
>>> This was my initial approach too, but argv[0] can be just the filename
>>> like "qemu-arm-static". And while I could add
Le 18/01/2016 05:33, Petros Angelatos a écrit :
> From: Petros Angelatos
>
> In order for one to use QEMU user mode emulation under a chroot, it is
> required to use binfmt_misc. This can be avoided by QEMU never doing a
> raw execve() to the host system.
>
> Introduce a
Hi Laurent,
> Are there some reasons to not use binfmt_misc when we are able to do
> chroot ?
>
> Moreover binfmt_misc allows to execute binaries that cannot be read, I
> think it is not possible with an userspace solution. And binfmt_misc
> also allows to use credential and security tokens from
Hi Petros,
Le 18/01/2016 05:33, Petros Angelatos a écrit :
> From: Petros Angelatos
>
> In order for one to use QEMU user mode emulation under a chroot, it is
> required to use binfmt_misc. This can be avoided by QEMU never doing a
> raw execve() to the host system.
Are
From: Petros Angelatos
In order for one to use QEMU user mode emulation under a chroot, it is
required to use binfmt_misc. This can be avoided by QEMU never doing a
raw execve() to the host system.
Introduce a new option, -execve=path, that sets the absolute path to the
QEMU