All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Laurent Vivier <laurent@vivier.eu>,
	qemu-devel@nongnu.org
Cc: Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] linux-user: manage binfmt-misc preserve-arg[0] flag
Date: Mon, 1 Mar 2021 14:16:47 +0300	[thread overview]
Message-ID: <185ce154-c34e-a417-69db-3d1da5609468@msgid.tls.msk.ru> (raw)
In-Reply-To: <6b0c8faf-98c8-29f7-a6be-7901b94deb38@physik.fu-berlin.de>

01.03.2021 14:07, John Paul Adrian Glaubitz wrote:
> On 3/1/21 11:40 AM, Michael Tokarev wrote:
>> 01.03.2021 13:35, John Paul Adrian Glaubitz wrote:
>> ..
>>> I have been trying to get qemu-user working with sbuild as it is shipped in Debian
>>> unstable now but I didn't have any success.
>>>
>>> Do you have some instructions somewhere how to get qemu-user working with sbuild?
>>
>> Have you seen #983087 which I fixed yesterday?
> 
> Thanks, but it doesn't help, unfortunately.
> 
> Do I need to use qemu-user-static or qemu-user-binfmt?

Oh. You tried to use qemu-user, not qemu-user-static..
Well.

In order for it to work it should be registered with the
in-kernel binfmt-misc subsystem. qemu-user-static package
does this automatically for you, but qemu-user does not,
for that with qemu-user you'll have to additionally install
qemu-user-binfmt package.

But I guess it wont work with qemu-user even if it is registered
(by means of installing qemu-user-binfmt or manual registration
or whatever), - because regular qemu-user binaries aren't
statically linked and hence require all the shared libraries
within the chroot in order to run.

I never tried to use regular (non-static) qemu-user with
foreign chroot, and I suspect it wont work because of that
very reason, and at least extra setup is needed (like
copying appropriate /lib/ld.so and libc&glib&Co to the
chroot).

This is all about how qemu-user works, be it debian or
any other distribution, - it is basically the same.
I can only guess the wiki page you mentioned is wrong
here.

Thanks,

/mjt



  reply	other threads:[~2021-03-01 11:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 10:50 [PATCH] linux-user: manage binfmt-misc preserve-arg[0] flag Laurent Vivier
2021-02-22 10:57 ` no-reply
2021-02-22 10:58 ` John Paul Adrian Glaubitz
2021-02-22 12:21   ` Laurent Vivier
2021-02-22 14:38   ` Michael Tokarev
2021-02-22 14:43     ` John Paul Adrian Glaubitz
2021-02-22 14:46       ` Michael Tokarev
2021-02-22 14:54         ` John Paul Adrian Glaubitz
2021-02-22 14:58           ` Michael Tokarev
2021-02-22 15:02             ` Helge Deller
2021-02-22 15:11               ` Michael Tokarev
2021-02-22 15:09             ` John Paul Adrian Glaubitz
2021-02-22 15:15               ` Michael Tokarev
2021-03-01 10:35             ` John Paul Adrian Glaubitz
2021-03-01 10:40               ` Michael Tokarev
2021-03-01 11:07                 ` John Paul Adrian Glaubitz
2021-03-01 11:16                   ` Michael Tokarev [this message]
2021-03-01 11:35                     ` John Paul Adrian Glaubitz
2021-02-22 14:45 ` Michael Tokarev
2021-02-22 17:09   ` Laurent Vivier
2021-02-22 20:07     ` Michael Tokarev
2021-03-09 20:15 ` Laurent Vivier
2021-09-06 18:00 ` Michael Tokarev

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=185ce154-c34e-a417-69db-3d1da5609468@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=deller@gmx.de \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=laurent@vivier.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.