This bug was fixed in the package qemu - 1:6.0+dfsg-2expubuntu1.1
---
qemu (1:6.0+dfsg-2expubuntu1.1) impish; urgency=medium
* updated debian/patches/linux-user-binfmt-P.diff to work with in-kernel code
(#993658) (LP: #1947860)
-- Christian Ehrhardt Wed, 03 Nov
2021
Verified on impish.
Before upgrade of qemu-user-static:
$ sudo chroot . echo 1 2 3
2 3
$
After upgrade:
$ sudo chroot . echo 1 2 3
1 2 3
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
** Changed in: qemu (Ubuntu Impish)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
Title:
qemu-arm-static swallows the program
This bug was fixed in the package qemu - 1:6.0+dfsg-2expubuntu2
---
qemu (1:6.0+dfsg-2expubuntu2) jammy; urgency=medium
* updated debian/patches/linux-user-binfmt-P.diff to work with in-kernel code
(#993658) (LP: #1947860)
-- Christian Ehrhardt Wed, 03 Nov
2021 14:10:56
FYI - there were two test issues in jammy-proposed, those are also
resolved by now and I hope it migrates there soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
Title:
qemu-arm-static
Before upgrade
#1 as outlined in the test instructions
ubuntu@i-qemu-static:~$ sudo chroot armTest-I echo 1 2 3
2 3
#2 as suggested by Seth with a chroot into an RPI image
$ wget
Thanks for the check Daniel!
Hi Seth,
if you consider getting an RPI (or any other) cross-arch image chrooted or to
run debootstrap is probably equally complex - and preference lies in what you
do more often or already have around. But thanks for the hint on test
alternatives.
BTW - I have
I have built 1:6.0+dfsg-2expubuntu1.1 on my own for Impish and this
patch solves my problems when building ARM packages on x86 using
pbuilder and docker-buildx. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
These test cases seem complicated to me. A reporter on IRC reported that
doing things within an rpi image chroot like 'mv a b' would report an
error message "missing destination file operand":
Fri 05 23:26:13 < five623468263> root@ubuntu:/# mv etc/resolv.conf
etc/resolv.conf.bak
Fri 05 23:26:13
Hello Kai, or anyone else affected,
Accepted qemu into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-2expubuntu1.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This is already in jammy-proposed by now, but due to a long test backlog on
ppc64 will be blocked there for a while.
Nevertheless that is enough to kick off the SRU of this, therefore I uploaded
it to Impish-unapproved already.
--
You received this bug notification because you are a member of
Given this really breaks cross-arch toolchains of all sorts I'm even
bumping this to critical.
** Changed in: qemu (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/411320
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/411321
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+
+ [Impact]
+
+ * The kernel changed handling of binfmt-P and that breaks qemu
+using binfmt registering TCG based emulators to run foreign
+architecture code.
+
+ * This happened late 5.11.0-20 -> 5.13.0-20 and even as of today
+cloud-images start with
I have site down and eventually together with paride was able to create
a bit of a timeline and a fix.
I have - at first - wondered as I could reproduce it in Jammy, but not in Impish
I had qemu 1:6.0+dfsg-2expubuntu1 in both, why would they behave different.
And then I found that my Impish
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
Title:
qemu-arm-static swallows the program name,
** Description changed:
Problem with qemu-arm-static version 1:6.0+dfsg-2expubuntu1, as of recent
Impish
When using qemu-arm-static for cross-debootstrap for an ARM machine argument
0 of the invoked ARM program does not contain the name of the executable but
argument 1, argument 2 is
Just a note: qemu-arm-static itself has nothing to do with it. I tried
older versions from hirsute and focal, and they exhibit the same
behaviour.
I can however confirm that the problem lies in the binfmt-P logic
handling - if I re-register qemu-arm-static manually without the
binfmt-P flag, it
And the assumption in
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1948684/comments/3 :
Björn Töpel (bjorn-topel) wrote 16 minutes ago: #3
This might have been fixed in Debian. From the changelog:
qemu (1:6.1+dfsg-5) unstable; urgency=medium
* updated
bug 1948684 reported almost the same (but for risc in qmeu user static).
Carrying the great Info generated by Björn there over here to handle it in one
place.
Steps to reproduce (using golang for ease of cross-compiling):
--
$ cat rv.go
package main
import (
"fmt"
"os"
)
func main() {
Here as well I want to be honest - I'm almost totally unavailable this
week so it will be a few more days before I can take a deeper look.
Thanks Björn for this debugging already!
Thanks for Paride for already confirming the reproducibility of this!
And to Andrew for an equally great report!
**
Upgrading to Debian sid version 1:6.1 also appears to resolve the issue:
Package: qemu-user-static/now 1:6.1+dfsg-6 amd64
$ sudo chroot armTest ./test.sh a bb ccc
$0=./test.sh
$1=a
$1=bb
$*=a bb ccc
$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm seeing a slight variation of this with
Package: qemu-user-static/impish,now 1:6.0+dfsg-2expubuntu1 amd64
Uname: Linux 5.13.0-21-generic #21-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
$ sudo chroot armTest ./test.sh a bb ccc
/bin/sh: 0: Can't open a
$ sudo chroot armTest ./test.sh ./test.sh
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
Title:
qemu-arm-static swallows the program name, and shifts all arguments
left
Hello and thanks for this bug report. I can confirm this issue,
reproduced by:
# With qemu-user-static 1:5.2+dfsg-9ubuntu3.2 (Hirsute):
$ sudo chroot armTest /usr/bin/echo 1 2 3
1 2 3
# With qemu-user-static 1:6.0+dfsg-2expubuntu1 (Impish/Jammy):
$ sudo chroot armTest /usr/bin/echo 1 2 3
2 3
** Tags added: qemu-arm-static qemu-user-static
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947860
Title:
qemu-arm-static swallows the program name, and shifts all arguments
left
To manage
26 matches
Mail list logo
