Debian Bug report logs - #306637
Please register qemu to binfmt mecanism (using binfmt-support?)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Martin Quinson <mquinson@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Wed, 27 Apr 2005 21:44:10 +0200

Package: qemu
Version: 0.6.1+20050407-1
Severity: wishlist

Hello,

it would be great if you could do the necessary so that foreign binaries
could be run automatically within qemu. It looks like the binfmt-support
package is exactly what we need for that. 

I didn't took the time to actually write the patch, though, sorry.

Bye, Mt.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

Versions of packages qemu depends on:
ii  bochsbios     2.1.1+20041109-3           BIOS for the Bochs emulator
ii  libc6         2.3.2.ds1-20               GNU C Library: Shared libraries an
ii  libsdl1.2debi 1.2.7+1.2.8cvs20041007-4.1 Simple DirectMedia Layer
ii  vgabios       0.5a-1                     VGA BIOS software for the Bochs an
ii  zlib1g        1:1.2.2-3                  compression library - runtime

-- no debconf information

Message #10 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Riku Voipio <Riku.Voipio@iki.fi>

To: Martin Quinson <mquinson@debian.org>, 306637@bugs.debian.org

Subject: Re: Bug#306637: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Fri, 29 Apr 2005 22:40:15 +0300

On Wednesday 27 April 2005 22:44, Martin Quinson wrote:
> it would be great if you could do the necessary so that foreign binaries
> could be run automatically within qemu. It looks like the binfmt-support
> package is exactly what we need for that.

We need actually a static qemu binary for that first. It is on the list of 
planned things thou :)

> I didn't took the time to actually write the patch, though, sorry.

<advert>Meanwhile, just use scratchbox</advert>

Message #15 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Martin Quinson <martin.quinson@loria.fr>

To: Riku Voipio <Riku.Voipio@iki.fi>

Cc: Martin Quinson <mquinson@debian.org>, 306637@bugs.debian.org

Subject: Re: Bug#306637: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Sat, 30 Apr 2005 14:14:51 +0200

[Message part 1 (text/plain, inline)]

On Fri, Apr 29, 2005 at 10:40:15PM +0300, Riku Voipio wrote:
> On Wednesday 27 April 2005 22:44, Martin Quinson wrote:
> > it would be great if you could do the necessary so that foreign binaries
> > could be run automatically within qemu. It looks like the binfmt-support
> > package is exactly what we need for that.
> 
> We need actually a static qemu binary for that first. It is on the list of 
> planned things thou :)

Yes? You really need a static binary to use binfmt? I don't remember reading
this. But I have to admit that I'm far from being a specialist of this.
Thanks for the hint, I won't give it a try if it's impossible ;)

> > I didn't took the time to actually write the patch, though, sorry.
> 
> <advert>Meanwhile, just use scratchbox</advert>

Why aren't the debian package not distributed within the main distribution?


Bye, Mt.

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Martin Quinson <martin.quinson@loria.fr>

To: 306637@bugs.debian.org

Subject: [pkg-qemu-devel-admin@lists.alioth.debian.org: Your message to pkg-qemu-devel awaits moderator approval]

Date: Sat, 30 Apr 2005 20:55:20 +0200

[Message part 1 (text/plain, inline)]

Please fix the settings of this mailing list or provide a sane packager
address.

Mt.

----- Forwarded message from pkg-qemu-devel-admin@lists.alioth.debian.org -----

Date: Sat, 30 Apr 2005 16:40:04 +0000
Subject: Your message to pkg-qemu-devel awaits moderator approval
From: pkg-qemu-devel-admin@lists.alioth.debian.org
To: martin.quinson@loria.fr

Your mail to 'pkg-qemu-devel' with the subject

    Bug#306637: Please register qemu to binfmt mecanism (using
binfmt-support?)

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.

----- End forwarded message -----

[signature.asc (application/pgp-signature, inline)]

Message #25 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: 306637@bugs.debian.org

Subject: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Mon, 27 Feb 2006 01:25:27 -0400

[Message part 1 (text/plain, inline)]

Package: qemu
Version: 0.8.0-2
Severity: wishlist

Hi,

I've attached a .debdiff that implements the requirements of this bug
(plus some minor bugfixes I found along the way). I've also put some
usage documentation at http://wiki.debian.org/QemuUserEmulation. Feel
free to correct/extend it as necessary.

Regards,
--
Anderson Lizardo
Embedded Linux Lab - 10LE
Nokia Institute of Technology - INdT
Manaus - Brazil

[qemu_0.8.0-3.debdiff (application/octet-stream, attachment)]

Message #30 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: 306637@bugs.debian.org

Subject: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Tue, 28 Feb 2006 23:51:13 -0400

[Message part 1 (text/plain, inline)]

Package: qemu
Version: 0.8.0-2
Severity: wishlist
Tags: patch

Attached an updated version of the patch with some fixes, including
implementation of some syscalls necessary to use qemu with
debootstrap.

I've renamed the patch name to avoid confusion with to which version it applies.

[qemu-0.8.0-2_binfmt.patch (text/x-patch, attachment)]

Message #37 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: 306637@bugs.debian.org

Subject: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Tue, 7 Mar 2006 16:53:56 -0400

[Message part 1 (text/plain, inline)]

Package: qemu
Version: 0.8.0-2
Severity: important
Tags: patch

New patch with some more bugs fixed, including a bugfix from Ulrich
Hecht, not in QEMU CVS yet. I'm also increasing bug severity to
"important" as (1) there is a patch available, so it's not a
"wishlist" anymore and (2) the patch has some fixes for real bugs
included.

I can also send separate bug reports for the bugs fixed in this patch
if necessary.

Changelog:

  * Fix package build/clean/build bugs.
  * Remove "--enable-slirp" configure flag, as it's default now.
  * Add build-stamp target to workaround "patch" target bug where "build" is
    run twice.
  * Fix ARM floating point emulation bug.
    - debian/patches/41_nwfpe_cpsr.patch: New file.
    Thanks to Ulrich Hecht.
  * Implement syscalls necessary to run debootstrap.
    - debian/patches/35_syscall_prctl.patch: New file.
    - debian/patches/36_syscall_mount.patch: New file.
    - debian/patches/37_syscall_arm_statfs64.patch: New file.
  * Add binfmt-support hooks, allowing "transparent" user emulation. Idea
    borrowed from qemu-binfmt-conf.sh.
  * Change default interpreter prefix to match dpkg-cross crossdir.
  * Add qemu-user-static package.

[qemu-0.8.0-2_binfmt-2.patch (text/x-patch, attachment)]

Message #44 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Guillem Jover <guillem@debian.org>

To: Anderson Lizardo <anderson.lizardo@gmail.com>, 306637@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#306637: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Wed, 8 Mar 2006 23:03:57 +0200

severity 306637 wishlist
thanks

Hi,

On Tue, Mar 07, 2006 at 04:53:56PM -0400, Anderson Lizardo wrote:
> Package: qemu
> Version: 0.8.0-2
> Severity: important
> Tags: patch

> New patch with some more bugs fixed, including a bugfix from Ulrich
> Hecht, not in QEMU CVS yet.

I'm aware of this bug fix, it has hit me when using sbox, so it's
going to be in next release.

> I'm also increasing bug severity to "important" as (1) there is a
> patch available, so it's not a "wishlist" anymore and (2) the patch
> has some fixes for real bugs included.

No, that's wrong, a bug does not stop being wishlist because it gets a
patch. And you should not try to sneak in unrelated and cosmetical
changes into an existing bug report. For new stuff, please file new
bug reports. I can agree though that the arm floating point comparision
could be important.

> I can also send separate bug reports for the bugs fixed in this patch
> if necessary.

> Changelog:
> 
>   * Fix package build/clean/build bugs.

Yes, hit that sometime ago, but forgot to fix. O:)

>   * Remove "--enable-slirp" configure flag, as it's default now.

Sure.

>   * Add build-stamp target to workaround "patch" target bug where "build" is
>     run twice.

patch has already its own stamp file, and I prefer not to have build
stamp files, otherwise you may modify something and it does not get
rebuilt.

>   * Fix ARM floating point emulation bug.
>     - debian/patches/41_nwfpe_cpsr.patch: New file.
>     Thanks to Ulrich Hecht.

This was under my radar already. :)

>   * Implement syscalls necessary to run debootstrap.
>     - debian/patches/35_syscall_prctl.patch: New file.
>     - debian/patches/36_syscall_mount.patch: New file.
>     - debian/patches/37_syscall_arm_statfs64.patch: New file.

Those should be in a new bug report.

>   * Add binfmt-support hooks, allowing "transparent" user emulation. Idea
>     borrowed from qemu-binfmt-conf.sh.

I don't like the way it's implemented, hardcoding the binary list is
prone to error, and the handling code for binfmt files could be greatly
reduced.

>   * Change default interpreter prefix to match dpkg-cross crossdir.

This should probably be in accordance with the multi-arch proposal
instead.

>   * Add qemu-user-static package.

But I'm not yet sure about providing the static binaries. It makes
security support harder in case of bugs found in linked libraries
for example.

Thanks for the patch and interest, though. =)

reagrds,
guillem

Message #51 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: "Guillem Jover" <guillem@debian.org>, 306637@bugs.debian.org

Subject: Re: Bug#306637: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Thu, 9 Mar 2006 01:18:24 -0400

Hi,

On 3/8/06, Guillem Jover <guillem@debian.org> wrote:
> On Tue, Mar 07, 2006 at 04:53:56PM -0400, Anderson Lizardo wrote:
> > New patch with some more bugs fixed, including a bugfix from Ulrich
> > Hecht, not in QEMU CVS yet.
>
> I'm aware of this bug fix, it has hit me when using sbox, so it's
> going to be in next release.

Ok. I'll post a different bug report for this issue then, so it does
not get forgotten :)

> > I'm also increasing bug severity to "important" as (1) there is a
> > patch available, so it's not a "wishlist" anymore and (2) the patch
> > has some fixes for real bugs included.
>
> No, that's wrong, a bug does not stop being wishlist because it gets a
> patch. And you should not try to sneak in unrelated and cosmetical
> changes into an existing bug report. For new stuff, please file new
> bug reports. I can agree though that the arm floating point comparision
> could be important.

Sorry about that. I think I have missunderstood the "severity" field meaning.

I'll issue separate bug reports for the different fixes/features (with
patches attached). BTW, is there any estimate date for the next
revision release? So I could prepare the patches before that date.

> >   * Add build-stamp target to workaround "patch" target bug where "build" is
> >     run twice.
>
> patch has already its own stamp file, and I prefer not to have build
> stamp files, otherwise you may modify something and it does not get
> rebuilt.

Sure, but there is an disavadvange of not having a build-stamp: the
"build" target is always run twice, once when dpkg-buildpackage runs
"./debian/rules build" and then again when running "./debian/rules
binary" (which depends on build). It's just not noticed because the
second "make" will usually have nothing to do.

This is really an issue when you create -static flavors of the
package, because the second run will overwrite the statically linked
binaries before they even get installed. Another (and better IMHO)
option would be to have the qemu source as a tarball that is unpacked
before running configure, just like the gcc source package. This way
each build "flavor" (static/shared) gets it's own tree and they don't
overwrite each other results. And more: the "clean" target becomes a
simple rm -rf of the build tree(s).

> >   * Add binfmt-support hooks, allowing "transparent" user emulation. Idea
> >     borrowed from qemu-binfmt-conf.sh.
>
> I don't like the way it's implemented, hardcoding the binary list is
> prone to error, and the handling code for binfmt files could be greatly
> reduced.

You mean having all those *.binfmt files in the debian/ directory?
Actually, those were created by running this awk script:

awk -F: '/echo/{printf "cat > qemu-"$2".binfmt << \"EOF\"\npackage
qemu\ninterpreter "$7"\nmagic "$5"\nmask "$6"\nEOF\n\n"}'
qemu-binfmt-conf.sh

It generates a script that can be piped to "bash" to generate the files.

Regarding the postinst and prerm scripts, they can indeed be
simplified by assuming all /usr/share/binfmts/qemu-* files were
installed by qemu.

> >   * Change default interpreter prefix to match dpkg-cross crossdir.
>
> This should probably be in accordance with the multi-arch proposal
> instead.

Sorry, I'm still new to the Debian development discussions... What
would be that "multi-arch proposal" ? Something like /lib64 for AMD64
? If so, It would in fact only work for those architectures where this
is supported (basically 32/64-bit variations).

The basic idea behind setting the default interpreter prefix to the
same as dpkg-cross basedir is to facilitate running binaries from
totally different architectures, e.g. run ARM binaries on i386
transparently, mainly because dpkg-cross greatly helps installing
non-native .deb's in a base directory suitable for using with qemu
user mode emulators. See http://wiki.debian.org/QemuUserEmulation for
an example of how easy that could be.

> >   * Add qemu-user-static package.
>
> But I'm not yet sure about providing the static binaries. It makes
> security support harder in case of bugs found in linked libraries
> for example.

Well, I surely agree on the security issues, but see these points:

- qemu-user-static contains only the user mode emulators, not the
system ones (qemu-system-*)
- qemu-$CPU binaries depend on few libraries (actually only standard
glibc libraries as seen by ldd).
- in order to use qemu emulation inside a non-native chroot (necessary
for cross-debootstrapping, for example), it needs to be statically
linked. Otherwise it would try to load libraries from /lib which are
actually non-native libraries. I've tried using some LD_LIBRARY_PATH
hacks, but they are not as effective as I would want.

Thanks,
--
Anderson Lizardo
Embedded Linux Lab - 10LE
Nokia Institute of Technology - INdT
Manaus - Brazil

Message #56 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: 306637@bugs.debian.org

Subject: Re: Bug#306637: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Sat, 11 Mar 2006 00:33:57 -0400

[Message part 1 (text/plain, inline)]

Package: qemu
Version: 0.8.0-2
Severity: wishlist
Tags: patch

New patch version, now reduced to just the binfmt changes. The other
changes were moved to separate bug reports. Note that this patch
depends on #356309 being applied first.

Changes since last version:
  - removed hard-coded binary lists from debian/rules and
prerm/postinst scripts.
  - removed qemu-user-static package creation (will move it to another
bug report, since it's not necessary to run executables transparently
outside of a chroot).

Changelog:

  * Add binfmt-support hooks, allowing "transparent" user emulation. Idea
    borrowed from qemu-binfmt-conf.sh.
    - Recommends binfmt-support.

--
Anderson Lizardo
Embedded Linux Lab - 10LE
Nokia Institute of Technology - INdT
Manaus - Brazil

[qemu_0.8.0-2_binfmt-3.patch (text/x-patch, attachment)]

Message #61 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: 306637@bugs.debian.org

Subject: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Sat, 11 Mar 2006 22:59:02 -0400

[Message part 1 (text/plain, inline)]

Package: qemu
Version: 0.8.0-2
Severity: wishlist
Tags: patch

New version, modified to apply after #356279
(qemu_0.8.0-2_build_outside_tree.patch). Also fixed a bug in
postinst/prerm scripts.

--
Anderson Lizardo
Embedded Linux Lab - 10LE
Nokia Institute of Technology - INdT
Manaus - Brazil

[qemu_0.8.0-2_binfmt-4.patch (text/x-patch, attachment)]

Message #66 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Anderson Lizardo" <anderson.lizardo@gmail.com>

To: 306637@bugs.debian.org

Subject: Please register qemu to binfmt mecanism (using binfmt-support?)

Date: Sun, 29 Oct 2006 22:13:43 -0400

[Message part 1 (text/plain, inline)]

Package: qemu
Version: 0.8.2-1
Severity: normal
Tags: patch

New patch version, using a new approach: the binfmt support comes now
in a separate "qemu-binfmt" package which does not affect the main
qemu package in any way. Enabling "transparent" user emulation is as
simple as "apt-get install qemu-binfmt".

Changelog:

 * Add binfmt-support hooks, allowing "transparent" user emulation. Idea
   borrowed from qemu-binfmt-conf.sh.
   - New package: qemu-binfmt.

-- 
Anderson Lizardo

[qemu_0.8.2-1_binfmt-5.patch (text/x-patch, attachment)]

Message #71 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Robert Millan <rmh@aybabtu.com>

To: 306637@bugs.debian.org

Cc: Anderson Lizardo <anderson.lizardo@gmail.com>

Subject: qemu and binfmt

Date: Sat, 28 Apr 2007 22:10:40 +0200

Hi,

I have some comments about this bug:

 - Are you sure #384338 blocks it?  See my last mail to that bug.

 - Why is a separate package needed?  non-native binaries are of no use without
   qemu/binfmt, so it doesn't harm to make them runable by default.

 - Why using intermediate wrappers instead of making qemu-$ARCH the interpreter?

 - Is there any mechanism to prevent:
   - infin loops when running native binaries
   - e.g. qemu-i386 being used on amd64 instead of native biarch.
   (or is that not necessary at all, because Linux will never fallback to
   binfmt on those?)

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.

Message #74 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Robert Millan <rmh@aybabtu.com>

To: 306637@bugs.debian.org

Cc: Anderson Lizardo <anderson.lizardo@gmail.com>

Subject: Re: qemu and binfmt

Date: Sat, 28 Apr 2007 22:19:14 +0200

On Sat, Apr 28, 2007 at 10:10:40PM +0200, Robert Millan wrote:
>  - Why using intermediate wrappers instead of making qemu-$ARCH the interpreter?

Ah, didn't notice the "-L $CROSS_PREFIX".  That explains it.

But then, I don't think it's a good idea to hardcode a path in CROSS_PREFIX
that relies in multiarch, since all that's unimplemented yet.

If people want to use this feature, they will have built a chroot (since
currently there's no other way).  I think for now it'd be better to just
provide the support so that users can do:

  /srv/chroot/i386/lib/ld-linux.so.2 /srv/chroot/i386/bin/foo

Instead of:

  qemu-i386 /srv/chroot/i386/lib/ld-linux.so.2 /srv/chroot/i386/bin/foo

Or maybe make CROSS_PREFIX a configurable option?

In that case, how about using the full path to ld.so as argument rather than
-L ? Sounds more flexible to me, since it doesn't assume any particular
filesystem structure to be setup (dynamic linking will work fine if you
setup /etc/ld.so.conf to whatever your needs are).

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.

Message #79 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Javier Serrano Polo <jasp00@terra.es>

To: 384338@bugs.debian.org

Cc: Simon Richter <sjr@debian.org>, 306637@bugs.debian.org

Subject: Re: qemu: please build static variants for use inside chroots

Date: Thu, 06 Mar 2008 02:15:05 +0100

You don't need static variants.
I'm bootstrapping a ppc chroot on amd64 with binfmt-support and normal
qemu. The command

        chroot ppc-linux/ date

just prints the date.

Message #84 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Simon Richter <sjr@debian.org>

To: Javier Serrano Polo <jasp00@terra.es>

Cc: 384338@bugs.debian.org, 306637@bugs.debian.org

Subject: Re: qemu: please build static variants for use inside chroots

Date: Thu, 20 Mar 2008 16:58:24 +0100

Hi,

Javier Serrano Polo wrote:

> You don't need static variants.
> I'm bootstrapping a ppc chroot on amd64 with binfmt-support and normal
> qemu.

How does this work? The kernel needs to load qemu from inside the chroot 
at this point, including all of the libraries, so these need to be 
installed into the chroot -- hence my request to have a static build so 
I only need to install (and keep track of) a single file whose name I 
can also choose (as opposed to libraries' names) so I can avoid 
conflicts with the actual chroot.

   Simon

Message #89 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Stuart Anderson <anderson@netsweng.com>

To: 306637@bugs.debian.org

Cc: 384338@bugs.debian.org

Subject: Re: Bug#306637: qemu: please build static variants for use inside chroots

Date: Thu, 20 Mar 2008 13:01:22 -0400 (EDT)

On Thu, 20 Mar 2008, Simon Richter wrote:

> Hi,
>
> Javier Serrano Polo wrote:
>
>> You don't need static variants.
>> I'm bootstrapping a ppc chroot on amd64 with binfmt-support and normal
>> qemu.
>
> How does this work? The kernel needs to load qemu from inside the chroot
> at this point, including all of the libraries, so these need to be
> installed into the chroot -- hence my request to have a static build so
> I only need to install (and keep track of) a single file whose name I
> can also choose (as opposed to libraries' names) so I can avoid
> conflicts with the actual chroot.

This is correct. Static linking is needed in some cases. There are certain
combinations of host and target where things like /lib/ld-linux.so.2
collide and thus you can't have both the host & target versions in the
chroot at the same time.


                                Stuart

Stuart R. Anderson                               anderson@netsweng.com
Network & Software Engineering                   http://www.netsweng.com/
1024D/37A79149:                                  0791 D3B8 9A4C 2CDC A31F
                                                 BD03 0A62 E534 37A7 9149

Message #94 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 306637@bugs.debian.org, 384338@bugs.debian.org

Subject: qemu: support binfmt and static build of qemu

Date: Mon, 20 Jul 2009 08:50:34 -0700

i've managed to use the packages from here:

  https://wiki.ubuntu.com/ARM/BuildEABIChroot

to build an armel chroot on i386, using debootstrap's --foreign/--second-stage
options, which was pretty slick. chrooting into it also worked like a charm.

there's also a bug on ubuntu to possibly include it all in future versions:

  https://bugs.launchpad.net/debian/+source/qemu/+bug/401782

is that a good starting point to move towards resolving these bugs?

live well,
  vagrant

Message #101 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "W. Martin Borgert" <debacle@debian.org>

To: 306637@bugs.debian.org, 384338@bugs.debian.org

Subject: Ubuntu package works for Debian

Date: Tue, 25 Aug 2009 20:54:53 +0200

I use the qemu-arm-static 0.11.0~rc1 package from here:
http://archive.ubuntu.com/ubuntu/pool/universe/q/qemu-kvm/
under Debian sid and it seems to work fine. I used the
binary i386 package and did not compile myself, ouch :~)

Message #108 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 306637@bugs.debian.org

Subject: register qemu-user-static with binfmt

Date: Tue, 24 Nov 2009 13:48:42 -0800

 commit 7b2fc8ab143a30fabfd1b867c3c150c38ca3fa22
 Author: Aurelien Jarno <aurelien@aurel32.net>
 Date:   Tue Nov 24 13:49:22 2009 +0100

      * qemu-user-static: register QEMU with binfmt mecanism. Closes:
        #306637.

i noticed this commit to git, but wanted to make sure that the fix included a
mechanism to exclude the running architecture. otherwise qemu will be used to
run all system binaries, no? or is there something i'm missing here?

live well,
  vagrant

Message #113 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Vagrant Cascadian <vagrant@freegeek.org>, 306637@bugs.debian.org

Subject: Re: Bug#306637: register qemu-user-static with binfmt

Date: Wed, 25 Nov 2009 06:38:03 +0100

On Tue, Nov 24, 2009 at 01:48:42PM -0800, Vagrant Cascadian wrote:
>  commit 7b2fc8ab143a30fabfd1b867c3c150c38ca3fa22
>  Author: Aurelien Jarno <aurelien@aurel32.net>
>  Date:   Tue Nov 24 13:49:22 2009 +0100
> 
>       * qemu-user-static: register QEMU with binfmt mecanism. Closes:
>         #306637.
> 
> i noticed this commit to git, but wanted to make sure that the fix included a
> mechanism to exclude the running architecture. otherwise qemu will be used to
> run all system binaries, no? or is there something i'm missing here?
> 
> live well,

I have tried here, and the running architecture still has the priority
over binfmt. 

The problem of excluding the running architecture is that you have to 
use a map between qemu and debian architecture, and the map is not
always 1:1. For example qemu-arm executes both arm and armel code.
OTOH sparc code can be executed either by qemu-sparc or 
qemu-sparc64abi32 depending if it needs a 32 or 64-bit CPU.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

Message #118 received at 306637@bugs.debian.org (full text, mbox, reply):

From: "Eugene V. Lyubimkin" <jackyf.devel@gmail.com>

To: 306637@bugs.debian.org

Subject: cannot be used in chroots?

Date: Thu, 3 Dec 2009 10:41:07 +0200

Hi Aurelien,

I attempted to build qemu from the current git debian-unstable branch, and it 
seems that such implementation of binfmt support doesn't allow chrooting into 
foreign target systems using qemu.

$ sudo chroot /srv/schroot/sid-armel/ ls
chroot: failed to run command `ls': Exec format error

$ ls -l /srv/schroot/sid-armel/{usr/bin/qemu-arm-static,usr/lib/qemu-user-
static/*}
-rwxr-xr-x 1 root root 1350244 Dec  2 15:08 /srv/schroot/sid-
armel/usr/bin/qemu-arm-static
-rwxr-xr-x 1 root root     684 Dec  3 10:08 /srv/schroot/sid-
armel/usr/lib/qemu-user-static/qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  3 10:32 /srv/schroot/sid-
armel/usr/lib/qemu-user-static/qemu-binfmt-arm -> qemu-binfmtfs/binfmt_misc/

$ ls -l /{usr/bin/qemu-arm-static,usr/lib/qemu-user-static/*}
-rwxr-xr-x 1 root root 1350244 Dec  2 10:48 /usr/bin/qemu-arm-static
-rwxr-xr-x 1 root root     684 Dec  2 10:02 /usr/lib/qemu-user-static/qemu-
binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-alpha -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-arm -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-armeb -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-cris -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-i386 -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-m68k -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-microblaze -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-mips -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-mipsel -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-ppc -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-ppc64 -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-ppc64abi32 -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-sh4 -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-sh4eb -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-sparc -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-sparc32plus -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-sparc64 -> qemu-binfmt
lrwxrwxrwx 1 root root      11 Dec  2 14:45 /usr/lib/qemu-user-static/qemu-
binfmt-x86_64 -> qemu-binfmt

I coundn't debug it much so I'm not sure, but I suspect this is because the 
binfmt qemu-through format is registered on shell script wrapper 
(/usr/lib/qemu-user-static/qemu-binfmt-arm), and when you chroot, there is no 
native script interpreter available to execute that wrapper.

The invocation without chrooting works well:

$ LD_LIBRARY_PATH=/srv/schroot/sid-armel/usr/lib:/srv/schroot/sid-armel/lib 
/srv/schroot/sid-armel/bin/ls
build  Desktop  download

Message #123 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: "Eugene V. Lyubimkin" <jackyf.devel@gmail.com>, 306637@bugs.debian.org

Subject: Re: Bug#306637: cannot be used in chroots?

Date: Mon, 7 Dec 2009 18:57:23 -0800

On Thu, Dec 03, 2009 at 10:41:07AM +0200, Eugene V. Lyubimkin wrote:
> I attempted to build qemu from the current git debian-unstable branch, and it 
> seems that such implementation of binfmt support doesn't allow chrooting into 
> foreign target systems using qemu.

i can confirm this.

i'd rather see just using /usr/bin/qemu-$ARCH-static directly, which allows you
to simply copy a single file into the chroot to get cross-architecture
chrooting to work. i have a git branch with those changes ready.

alternately, since a wrapper might be useful, at least make the qemu-$ARCH
binfmt files that get loaded configurable somehow. making
/usr/share/binfmts/qemu-* symlinks to conffiles in /etc might be one way to
accomplish this.

live well,
  vagrant

Message #128 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Vagrant Cascadian <vagrant@freegeek.org>, 306637@bugs.debian.org

Cc: "Eugene V. Lyubimkin" <jackyf.devel@gmail.com>

Subject: Re: Bug#306637: cannot be used in chroots?

Date: Tue, 08 Dec 2009 14:02:57 +0100

Vagrant Cascadian a écrit :
> On Thu, Dec 03, 2009 at 10:41:07AM +0200, Eugene V. Lyubimkin wrote:
>> I attempted to build qemu from the current git debian-unstable branch, and it 
>> seems that such implementation of binfmt support doesn't allow chrooting into 
>> foreign target systems using qemu.
> 
> i can confirm this.
> 
> i'd rather see just using /usr/bin/qemu-$ARCH-static directly, which allows you
> to simply copy a single file into the chroot to get cross-architecture
> chrooting to work. i have a git branch with those changes ready.

Not using a wrapper forbids you to run cross architectures binaries
directly.

> alternately, since a wrapper might be useful, at least make the qemu-$ARCH
> binfmt files that get loaded configurable somehow. making
> /usr/share/binfmts/qemu-* symlinks to conffiles in /etc might be one way to
> accomplish this.

The problem with that, is that update-binfmt has to be rerun when those
files are changed.


The question is what is more useful to the user.

Being able to run a binary file from an architecture directly (provided
that you have the libraries unpack somewhere) looks a big improvement.
For this we need a wrapper.

Simplifying a single command line by being able to enter "chroot
/location" instead of "qemu-arm chroot /location" looks less useful.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

Message #133 received at 306637@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 306637@bugs.debian.org

Subject: Re: Bug#306637: cannot be used in chroots?

Date: Tue, 8 Dec 2009 21:37:23 -0800

On Tue, Dec 08, 2009 at 02:02:57PM +0100, Aurelien Jarno wrote:
> Vagrant Cascadian a écrit :
> > i'd rather see just using /usr/bin/qemu-$ARCH-static directly, which allows you
> > to simply copy a single file into the chroot to get cross-architecture
> > chrooting to work. i have a git branch with those changes ready.
> 
> Not using a wrapper forbids you to run cross architectures binaries
> directly.

ok.

> > alternately, since a wrapper might be useful, at least make the qemu-$ARCH
> > binfmt files that get loaded configurable somehow. making
> > /usr/share/binfmts/qemu-* symlinks to conffiles in /etc might be one way to
> > accomplish this.
> 
> The problem with that, is that update-binfmt has to be rerun when those
> files are changed.
 
sure.
 
> The question is what is more useful to the user.
> 
> Being able to run a binary file from an architecture directly (provided
> that you have the libraries unpack somewhere) looks a big improvement.
> For this we need a wrapper.
 
> Simplifying a single command line by being able to enter "chroot
> /location" instead of "qemu-arm chroot /location" looks less useful.

as best i can tell, that simply doesn't work:

  qemu-arm-static chroot /opt/ltsp/armel/
  Error -1 while loading chroot

the only point (that i'm aware of) for building static variants seemed to be
for simplified cross-architecture chroots, based on the bug report:

  #384338 qemu: please build static variants for use inside chroots

i've heard people requesting cross-architecture support for debootstrap,
lessdisks and LTSP for 5+ years, and it is feasible to have it working out of
the box (at least for some architectures) with qemu-user-static.

so i'd like to figure out something workable for both use cases, though i
admittedly am not familiar with the use cases for non-chrooted environments.

live well,
  vagrant

p.s. no need to CC me; i'm wathching the bug report and list.

Message #144 received at 306637-close@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurel32@debian.org>

To: 306637-close@bugs.debian.org

Subject: Bug#306637: fixed in qemu 0.11.1-1

Date: Sun, 27 Dec 2009 22:03:31 +0000

Source: qemu
Source-Version: 0.11.1-1

We believe that the bug you reported is fixed in the latest version of
qemu, which is due to be installed in the Debian FTP archive:

libqemu-dev_0.11.1-1_amd64.deb
  to main/q/qemu/libqemu-dev_0.11.1-1_amd64.deb
qemu-system_0.11.1-1_amd64.deb
  to main/q/qemu/qemu-system_0.11.1-1_amd64.deb
qemu-user-static_0.11.1-1_amd64.deb
  to main/q/qemu/qemu-user-static_0.11.1-1_amd64.deb
qemu-user_0.11.1-1_amd64.deb
  to main/q/qemu/qemu-user_0.11.1-1_amd64.deb
qemu-utils_0.11.1-1_amd64.deb
  to main/q/qemu/qemu-utils_0.11.1-1_amd64.deb
qemu_0.11.1-1.diff.gz
  to main/q/qemu/qemu_0.11.1-1.diff.gz
qemu_0.11.1-1.dsc
  to main/q/qemu/qemu_0.11.1-1.dsc
qemu_0.11.1-1_amd64.deb
  to main/q/qemu/qemu_0.11.1-1_amd64.deb
qemu_0.11.1.orig.tar.gz
  to main/q/qemu/qemu_0.11.1.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 306637@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated qemu package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 27 Dec 2009 12:09:11 +0100
Source: qemu
Binary: qemu qemu-system qemu-user qemu-user-static qemu-utils libqemu-dev
Architecture: source amd64
Version: 0.11.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian QEMU Team <pkg-qemu-devel@lists.alioth.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Description: 
 libqemu-dev - static libraries and headers for QEMU
 qemu       - fast processor emulator
 qemu-system - QEMU full system emulation binaries
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 306637 436094 447034 556301
Changes: 
 qemu (0.11.1-1) unstable; urgency=low
 .
   [ Aurelien Jarno ]
   * New upstream version.
   * Drop build-depends on libfreebsd-dev on GNU/kFreeBSD.
   * qemu: suggests qemu-user-static.
   * qemu-user-static: register QEMU with binfmt mecanism. Closes:
     #306637.
   * Bump conflicts on openbios-ppc to (<< 1.0+svn505-1).
   * Add 01-binutils-gold.diff to fix FTBFS with binutils-gold. Closes:
     #556301.
   * Add sparc64 support.
   * Use new roms location in etherboot package.
 .
   [ Vagrant Cascadian ]
   * qemu-utils, qemu-user, qemu-system: Set both Conflicts and Replaces for
     older versions of qemu to ensure proper upgrade path.
   * Add versioned build-dep on linux-libc-dev to ensure that KVM support is
     enabled.
   * qemu-system: Lower dependencies on vgabios, bochsbios, openhackware,
     openbios-ppc and openbios-sparc to recommends. Conflict with versions that
     are incompatible. Closes: #436094.
   * qemu-utils: Tighten the versioned conflicts with kvm, as not all older
     versions actually conflict.
   * qemu-make-debian-root: Apply modified patch from Nicolas Boulenguez that
     documents usage of -s, exits on error, and mentions that it is normally
     run as root. Closes: #447034.
Checksums-Sha1: 
 dd551fc32885b515a5f91dcee43f0929d7a0831b 1900 qemu_0.11.1-1.dsc
 d846806597bd64dc05837284778e9f1f567cef15 3233024 qemu_0.11.1.orig.tar.gz
 5c8840e8ea07ba52d8465c8262ea33fb8f75f94f 28534 qemu_0.11.1-1.diff.gz
 6e2a181fdee02d177c98eec4410913906a326154 95612 qemu_0.11.1-1_amd64.deb
 391dbd8a3dbdc87efedcbcbaa2cd6e07f34b6c08 13954458 qemu-system_0.11.1-1_amd64.deb
 6cdd6a7115271314e7a119f698d6bdbb375b01cf 5331780 qemu-user_0.11.1-1_amd64.deb
 aea280229162d84da323daebd09013d35e76f6cf 10404174 qemu-user-static_0.11.1-1_amd64.deb
 32b71cc83347ce7e4a4927dd5f93078c533d059f 303500 qemu-utils_0.11.1-1_amd64.deb
 fecd8fefdb5ecdac4ef73a03d9fe8d08e865caab 5378600 libqemu-dev_0.11.1-1_amd64.deb
Checksums-Sha256: 
 426ab31aa7d05eb3a40d352e67ee8e975796c5fd0ca972ca036640d8c0757380 1900 qemu_0.11.1-1.dsc
 861d06c4ccffa7773350d8d93db764d6c9d65f2cd50d9e40a2366a40329de7e2 3233024 qemu_0.11.1.orig.tar.gz
 9cebb1768e250d7658f59087384b8b81c5875c509a19d33e9e7c0977eb4dd47a 28534 qemu_0.11.1-1.diff.gz
 0a6b976dffd2dede8b2e3af6c08033981ba085779272954ea6ee7d5d777e4cc2 95612 qemu_0.11.1-1_amd64.deb
 50b0e7b3c8cf9fa3acd1c6087172fad5993829357f36af746aa52b165d78da37 13954458 qemu-system_0.11.1-1_amd64.deb
 aa85b14c42a83002108b3e4646edd7830cf0f4713fe43cf50ff5dce2be9622c8 5331780 qemu-user_0.11.1-1_amd64.deb
 63d77c316b5a770d51682903436a6349f5cb1dcab03c0e689b2489eb71d73a95 10404174 qemu-user-static_0.11.1-1_amd64.deb
 04ab63844ae2dcc881f27238440720a114cc8717acd87ef31d761274e01ed881 303500 qemu-utils_0.11.1-1_amd64.deb
 33d539642d162cf1356c884ed2b53239915a9bec5d761859212003d07401c162 5378600 libqemu-dev_0.11.1-1_amd64.deb
Files: 
 1bb1bee1f7844eeb15c89cf57991f7de 1900 misc optional qemu_0.11.1-1.dsc
 519a8261b0fe47fad96e27e85d02fb86 3233024 misc optional qemu_0.11.1.orig.tar.gz
 2854b6be49b616c102b98617948414e0 28534 misc optional qemu_0.11.1-1.diff.gz
 38a317a56c5e950accb5c99f700742ef 95612 misc optional qemu_0.11.1-1_amd64.deb
 f92acafb7ff0d2f9f6599c04a7b79865 13954458 misc optional qemu-system_0.11.1-1_amd64.deb
 7eced9eb1fda7971a6cacf1d977a0ccc 5331780 misc optional qemu-user_0.11.1-1_amd64.deb
 eadbbe848415ff59f1b872425f2c5ced 10404174 misc optional qemu-user-static_0.11.1-1_amd64.deb
 b6e813a0c4e99ac88cd7671c4220cc59 303500 misc optional qemu-utils_0.11.1-1_amd64.deb
 526f9828269a15a4837635db396acbed 5378600 libdevel optional libqemu-dev_0.11.1-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLN0LQw3ao2vG823MRAv3hAJ4w4N2flkbUoxacnGILs/9wBU15zACfQdAT
VuvUj9WMV++3uTCKdLqnxL4=
=K55n
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.