Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-11-11 Thread Michal Suchanek
Excerpts from Michael Tokarev's message of Tue Nov 11 08:33:40 +0100 2014:
 27.09.2014 18:10, Michael Tokarev wrote:
  Control: tag -1 moreinfo unreproducible
  
  27.09.2014 16:33, Michal Suchanek wrote:
  Package: qemu-user-binfmt
  Version: 2.1+dfsg-4
  Severity: normal
 
  Hello,
 
  I tried installing qemu-user-binfmt in the hope I will be able to run 
  foreign architecture binaries.
 
  This has absolutely no results. THe package is empty and foreign binaries 
  do not run.
  
  As stated in the package description, the package is empty and the only
  reason for it to exist is to run scripts at install and remove times to
  register binfmt support.  This is the reason why it depends on qemu-user
  (actual implementation) and binfmt-support (registration).
  
  Please be more specific. Which binaries you tried to run but failed?
  What error message did you get?  With the info you provided it is
  impossible to handle your bugreport, especially since I know this
  package works on my systems.
  
  Do you realize that in order to run regular foreign binary, you also
  need to install all (foreign) libraries required by that binary.  With
  plain qemu-user and without additional foreig libraries it is possible
  to run only statically linked foreign binaries.
  
  On the other hand you can create a whole foreign chroot with its own
  libraries and directory structure, and chroot into it using qemu as
  a helper/emulator -- but for this to work, now it is qemu who needs
  (now native) libraries inside the chroot, or you should use statically
  linked qemu.
  
  Interestingly, on machines where this works this plackage is not present.
 
  Is this package supposed to do anything?
  
  See above.
  
  If not what is the preferred way to run foreign binaries?
  
  I don't understand this question.  There's no True Way for anything.
  Depending on your needs, you may use qemu-user-binfmt or qemu-user-static,
  there may be other alternatives.

I found that I have qemu-user-static instead of qemu-user-binfmt on
system where this works. I can run armhf binaries on a PC but the
reverse does not work. There is a handler for PC binaries registered but
bash still reports it cannot execute binary file.

Is the magic for PC binaries correct? How do I check?


 
 Hello  Michal.  A friendly ping?  Do you have any additional information
 for this bugreport?  I can't do anything with it without your input...

I did send another email in the bug report, right?

Thanks

Michal


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-11-11 Thread Michael Tokarev
11.11.2014 11:02, Michal Suchanek wrote:
[]
 
 I found that I have qemu-user-static instead of qemu-user-binfmt on
 system where this works. I can run armhf binaries on a PC but the

Yes, I've seen that.

 reverse does not work. There is a handler for PC binaries registered but
 bash still reports it cannot execute binary file.
 
 Is the magic for PC binaries correct? How do I check?

I replied to that at the time, -- the same magic strings are used in
both packages (qemu-user-static and qemu-user-binfmt), these are
generated (using simple substitutions) from a common file.

 Hello  Michal.  A friendly ping?  Do you have any additional information
 for this bugreport?  I can't do anything with it without your input...
 
 I did send another email in the bug report, right?

Yes, and I replied to that, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763043#22


So, to rehash, do I understand it right that you're having
probs with running x86 binaries on arm, when using -user-binfmt
but not when using -user-static ?

Did you try using -user-binfmt on PC to run arm binaries, does
that work?  (I can try that myself, but I think I verified this).

Please note that -user-binfmt (the non-statically-linked variant)
will not work in a foreign chroot, since it needs not only the
qemu binary itself, but also all the libraries which are linked
dynamically into it.  But I think this does not apply since you
don't run foreign binaries in a chroot, at least as far as I can
understand.

Thanks,

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-11-11 Thread Michal Suchanek
Excerpts from Michael Tokarev's message of Tue Nov 11 09:15:15 +0100 2014:
 11.11.2014 11:02, Michal Suchanek wrote:
 []
  
  I found that I have qemu-user-static instead of qemu-user-binfmt on
  system where this works. I can run armhf binaries on a PC but the
 
 Yes, I've seen that.
 
  reverse does not work. There is a handler for PC binaries registered but
  bash still reports it cannot execute binary file.
  
  Is the magic for PC binaries correct? How do I check?
 
 I replied to that at the time, -- the same magic strings are used in
 both packages (qemu-user-static and qemu-user-binfmt), these are
 generated (using simple substitutions) from a common file.

Yes, neither works, unsurprisingly.

 
  Hello  Michal.  A friendly ping?  Do you have any additional information
  for this bugreport?  I can't do anything with it without your input...
  
  I did send another email in the bug report, right?
 
 Yes, and I replied to that, see
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763043#22
 
 
 So, to rehash, do I understand it right that you're having
 probs with running x86 binaries on arm, when using -user-binfmt
 but not when using -user-static ?

I am having problem running x86 binaries on arm with either package.

# strace ./app 
execve(./app, [./app], [/* 17 vars */]) = -1 ENOEXEC (Exec format
error)
write(2, strace: exec: Exec format error\n, 32strace: exec: Exec
format error
) = 32
exit_group(1)   = ?
+++ exited with 1 +++

# file app
app: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux),
statically linked, stripped

# uname -a
Linux sun5i 3.4.103+ #36 PREEMPT Thu Aug 28 17:40:10 CEST 2014 armv7l
GNU/Linux

There is probably problem with static binaries:

# apt-get install unrar:amd64
...
ldconfig: /lib/x86_64-linux-gnu/libz.so.1 is for unknown machine 62.
...
ldconfig: /lib/ld-linux.so.2 is for unknown machine 3.
...

# unrar /?
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

# apt-get install cdebootstrap-static:amd64

# cdebootstrap-static /?
-bash: /usr/bin/cdebootstrap-static: cannot execute binary file

Thanks

Michal


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-11-11 Thread Michael Tokarev
Control: retitle -1 x86 emulation does not work on arm host
Control: reassign -1 qemu-user
Control: tag -1 - moreinfo

11.11.2014 13:18, Michal Suchanek wrote:
[]
 So, to rehash, do I understand it right that you're having
 probs with running x86 binaries on arm, when using -user-binfmt
 but not when using -user-static ?
 
 I am having problem running x86 binaries on arm with either package.

Aha.  That is entirely different thing.  Retitling the bugreport
accordingly.  Please correct me if I'm wrong.

 # strace ./app 
 execve(./app, [./app], [/* 17 vars */]) = -1 ENOEXEC (Exec format
 error)
 write(2, strace: exec: Exec format error\n, 32strace: exec: Exec
 format error
 ) = 32
 exit_group(1)   = ?
 +++ exited with 1 +++
 
 # file app
 app: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux),
 statically linked, stripped
 
 # uname -a
 Linux sun5i 3.4.103+ #36 PREEMPT Thu Aug 28 17:40:10 CEST 2014 armv7l
 GNU/Linux
 
 There is probably problem with static binaries:
 
 # apt-get install unrar:amd64
 ...
 ldconfig: /lib/x86_64-linux-gnu/libz.so.1 is for unknown machine 62.
 ...
 ldconfig: /lib/ld-linux.so.2 is for unknown machine 3.
 ...
 
 # unrar /?
 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
 Segmentation fault
 
 # apt-get install cdebootstrap-static:amd64
 
 # cdebootstrap-static /?
 -bash: /usr/bin/cdebootstrap-static: cannot execute binary file

Ok. This makes sense.  Thanks, will try to look into this.

Thanks,

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-11-11 Thread Michal Suchanek
Excerpts from Michael Tokarev's message of Tue Nov 11 14:16:23 +0100 2014:
 11.11.2014 13:18, Michal Suchanek wrote:
 []
  So, to rehash, do I understand it right that you're having
  probs with running x86 binaries on arm, when using -user-binfmt
  but not when using -user-static ?
  
  I am having problem running x86 binaries on arm with either package.
 
 Aha.  That is entirely different thing.  Retitling the bugreport
 accordingly.  Please correct me if I'm wrong.

That's not entirely true. It only fails for static binaries and I
happened to have a statically linked application. I am able to run full
x86 wine at racing snail speed. Probably because it's dynamically
linked.

 
  # strace ./app 
  execve(./app, [./app], [/* 17 vars */]) = -1 ENOEXEC (Exec format
  error)
  write(2, strace: exec: Exec format error\n, 32strace: exec: Exec
  format error
  ) = 32
  exit_group(1)   = ?
  +++ exited with 1 +++
  
  # file app
  app: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux),
  statically linked, stripped
  
  # uname -a
  Linux sun5i 3.4.103+ #36 PREEMPT Thu Aug 28 17:40:10 CEST 2014 armv7l
  GNU/Linux
  
  There is probably problem with static binaries:
  
  # apt-get install unrar:amd64
  ...
  ldconfig: /lib/x86_64-linux-gnu/libz.so.1 is for unknown machine 62.
  ...
  ldconfig: /lib/ld-linux.so.2 is for unknown machine 3.
  ...
  
  # unrar /?
  qemu: uncaught target signal 11 (Segmentation fault) - core dumped
  Segmentation fault
  
  # apt-get install cdebootstrap-static:amd64
  
  # cdebootstrap-static /?
  -bash: /usr/bin/cdebootstrap-static: cannot execute binary file
 
 Ok. This makes sense.  Thanks, will try to look into this.
 

Thanks

Michal


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-11-10 Thread Michael Tokarev
27.09.2014 18:10, Michael Tokarev wrote:
 Control: tag -1 moreinfo unreproducible
 
 27.09.2014 16:33, Michal Suchanek wrote:
 Package: qemu-user-binfmt
 Version: 2.1+dfsg-4
 Severity: normal

 Hello,

 I tried installing qemu-user-binfmt in the hope I will be able to run 
 foreign architecture binaries.

 This has absolutely no results. THe package is empty and foreign binaries do 
 not run.
 
 As stated in the package description, the package is empty and the only
 reason for it to exist is to run scripts at install and remove times to
 register binfmt support.  This is the reason why it depends on qemu-user
 (actual implementation) and binfmt-support (registration).
 
 Please be more specific. Which binaries you tried to run but failed?
 What error message did you get?  With the info you provided it is
 impossible to handle your bugreport, especially since I know this
 package works on my systems.
 
 Do you realize that in order to run regular foreign binary, you also
 need to install all (foreign) libraries required by that binary.  With
 plain qemu-user and without additional foreig libraries it is possible
 to run only statically linked foreign binaries.
 
 On the other hand you can create a whole foreign chroot with its own
 libraries and directory structure, and chroot into it using qemu as
 a helper/emulator -- but for this to work, now it is qemu who needs
 (now native) libraries inside the chroot, or you should use statically
 linked qemu.
 
 Interestingly, on machines where this works this plackage is not present.

 Is this package supposed to do anything?
 
 See above.
 
 If not what is the preferred way to run foreign binaries?
 
 I don't understand this question.  There's no True Way for anything.
 Depending on your needs, you may use qemu-user-binfmt or qemu-user-static,
 there may be other alternatives.

Hello  Michal.  A friendly ping?  Do you have any additional information
for this bugreport?  I can't do anything with it without your input...

Thank you!

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-09-27 Thread Michal Suchanek
Package: qemu-user-binfmt
Version: 2.1+dfsg-4
Severity: normal

Hello,

I tried installing qemu-user-binfmt in the hope I will be able to run foreign 
architecture binaries.

This has absolutely no results. THe package is empty and foreign binaries do 
not run.

Interestingly, on machines where this works this plackage is not present.

Is this package supposed to do anything?

If not what is the preferred way to run foreign binaries?

Thanks

Michal

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (900, 'stable'), (510, 'unstable'), (505, 'experimental'), (500, 
'saucy-updates'), (500, 'saucy-security'), (500, 'saucy-proposed'), (500, 
'saucy'), (500, 'raring-updates'), (500, 'raring'), (500, 'testing'), (100, 
'saucy-backports')
Architecture: armhf (armv7l)

Kernel: Linux 3.4.0 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages qemu-user-binfmt depends on:
ii  binfmt-support  2.0.12
ii  qemu-user   2.1+dfsg-4

qemu-user-binfmt recommends no packages.

qemu-user-binfmt suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = en_US.UTF-8
are supported and installed on your system.
perl: warning: Falling back to the standard locale (C).
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-09-27 Thread Michael Tokarev
Control: tag -1 moreinfo unreproducible

27.09.2014 16:33, Michal Suchanek wrote:
 Package: qemu-user-binfmt
 Version: 2.1+dfsg-4
 Severity: normal
 
 Hello,
 
 I tried installing qemu-user-binfmt in the hope I will be able to run foreign 
 architecture binaries.
 
 This has absolutely no results. THe package is empty and foreign binaries do 
 not run.

As stated in the package description, the package is empty and the only
reason for it to exist is to run scripts at install and remove times to
register binfmt support.  This is the reason why it depends on qemu-user
(actual implementation) and binfmt-support (registration).

Please be more specific. Which binaries you tried to run but failed?
What error message did you get?  With the info you provided it is
impossible to handle your bugreport, especially since I know this
package works on my systems.

Do you realize that in order to run regular foreign binary, you also
need to install all (foreign) libraries required by that binary.  With
plain qemu-user and without additional foreig libraries it is possible
to run only statically linked foreign binaries.

On the other hand you can create a whole foreign chroot with its own
libraries and directory structure, and chroot into it using qemu as
a helper/emulator -- but for this to work, now it is qemu who needs
(now native) libraries inside the chroot, or you should use statically
linked qemu.

 Interestingly, on machines where this works this plackage is not present.
 
 Is this package supposed to do anything?

See above.

 If not what is the preferred way to run foreign binaries?

I don't understand this question.  There's no True Way for anything.
Depending on your needs, you may use qemu-user-binfmt or qemu-user-static,
there may be other alternatives.

Thanks,

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-09-27 Thread Michal Suchanek
Package: qemu-user-static
Version: 2.1+dfsg-4
Followup-For: Bug #763043

Hello,

I found that I have qemu-user-static instead of qemu-user-binfmt on system
where this works. I can run armhf binaries on a PC but the reverse does not
work. There is a handler for PC binaries registered but bash still reports it
cannot execute binary file.

Is the magic for PC binaries correct? How do I check?

Thanks

Michal

-- System Information:
Debian Release: 7.6
  APT prefers stable
  APT policy: (900, 'stable'), (510, 'unstable'), (505, 'experimental'), (500, 
'saucy-updates'), (500, 'saucy-security'), (500, 'saucy-proposed'), (500, 
'saucy'), (500, 'raring-updates'), (500, 'raring'), (500, 'testing'), (100, 
'saucy-backports')
Architecture: armhf (armv7l)

Kernel: Linux 3.4.0 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

qemu-user-static depends on no packages.

Versions of packages qemu-user-static recommends:
ii  binfmt-support  2.0.12

Versions of packages qemu-user-static suggests:
ii  sudo  1.8.5p2-1+nmu1

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#763043: qemu-user-binfmt: binfmt support broken - package empty, foreign binaries do not run

2014-09-27 Thread Michael Tokarev
27.09.2014 17:29, Michal Suchanek wrote:
 
 I found that I have qemu-user-static instead of qemu-user-binfmt on system
 where this works. I can run armhf binaries on a PC but the reverse does not
 work. There is a handler for PC binaries registered but bash still reports it
 cannot execute binary file.
 
 Is the magic for PC binaries correct? How do I check?

Exactly the same set of magic strings is used in qemu-user-static and 
qemu-user-binfmt.

Thanks,

/mjt


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org