Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #272440

Re: QEMU: Run a container of a different architecture

Show all headers | View raw

"Markus Schönhaber" writes:

> No. systemd-nspawn does indeed simply run a container. You can think of
> that as a chroot on steroids. This means, everything inside the
> container is run using the host kernel. Or to put it the other way
> round: what the host kernel can't execute won't run.

Actually, the kernel can execute such foreign ELF binaries.  This
works with the binfmt_misc file system and registering the appropriate
interpreter which is then automaically executed by the kernel.  This is
similar to the she-bang (!#) mechanism where the kernel also loads the
needed interpreter.

I've shown that in my mail with executing the aarch64 date binary
directly on the amd64 kernel.  I didn't see any reason why this
shouldn't work with all binaries in a container.  Now, when looking at
it again, I think the problem is the missing interpreter in the
container's file system.  Quite obvious.  OK, I'll try copying the
QEMU interpreter qemu-aarch64 and all needed libs and other files into
the appropriate place...

Steve

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

QEMU: Run a container of a different architecture Steve Keller <keller.steve@gmx.de> - 2024-08-21 17:20 +0200
  Re: QEMU: Run a container of a different architecture Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2024-08-21 19:10 +0200
    Re: QEMU: Run a container of a different architecture Steve Keller <keller.steve@gmx.de> - 2024-08-21 22:30 +0200
  Re: QEMU: Run a container of a different architecture Tim Woodall <debianuser@woodall.me.uk> - 2024-08-22 19:30 +0200
    Re: QEMU: Run a container of a different architecture Steve Keller <keller.steve@gmx.de> - 2024-08-23 16:30 +0200

csiph-web