** Changed in: qemu (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890881
Title:
qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf
This bug was fixed in the package qemu - 1:5.0-5ubuntu6
---
qemu (1:5.0-5ubuntu6) groovy; urgency=medium
* d/p/ubuntu/lp-1887935-vfio-ccw-allow-non-prefetch-ORBs.patch: fix boot
from vfio-ccw (LP: #1887935)
qemu (1:5.0-5ubuntu5) groovy; urgency=medium
* fix qemu-user-static
Thank you very much.
qemu-user-static1:5.0-5ubuntu5~ppa2
also works fine for me!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890881
Title:
qemu-user-static 1:5.0-5ubuntu4 in groovy does
FYI - Tried on the proposed PPA, working now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890881
Title:
qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf
container
To manage
FYI
MP for these fixes at:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/389514
PPA for the same at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4214/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There are a bunch of Fixes for this commit in 5.1 and some dependencies to
those.
These we need to pull in as well here - which makes it even less SRUable :-/
I guess we will fix it in Groovy (20.10) and users that rely on this
valid but rare use case can use groovy or -later on- the Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/389514
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890881
Title:
qemu-user-static
git bisect reset
git bisect start
git bisect old v5.0.0
git bisect new 65b261a63a
#And then on each stop:
git cherry-pick 65b261a63a
# And some tweaks to convince bisect to do the right thing
That brings me to:
commit ee94743034bfb443cf246eda4971bdc15d8ee066
Author: Alex Bennée
Date: Wed May
@Ryutaroh - yes the package updates thes on install/upgrades
But I needed something to do on bisect - well it worked and I found what is
needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890881
> Eventually I found I need to unimport it after exchanging the binary.
> Then I get it to use the new version.
Yes... I also needed to run "systemctl restart binfmt-format",
which looks equivalent.
After qemu-user-static package is upgraded, user space emulation sometimes
fails, so I suspect
Ignoring all changes later han RTM_SETLINK and those that sound related
I came to:
1 pick 13a0c21e64 linux-user/arm: BKPT should cause SIGTRAP, not be a syscall
2 pick 62f141a426 linux-user/arm: Remove bogus SVC 0xf0002 handling
3 pick ab546bd238 linux-user/arm:
So some other patch between 5.0 and 65b261a6 is required "as well" but
can't be seen in the bisecting as only later after 65b261a6 the test is
successful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
But that makes no sense, since that is the patch we already carry in
debian/patches/linux-user-add-netlink-RTM_SETLINK-command.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890881
Title:
commit 65b261a63a48fbb3b11193361d4ea0c38a3c3dfd
Author: Laurent Vivier
Date: Thu Jul 9 09:23:32 2020 +0200
linux-user: add netlink RTM_SETLINK command
This command is needed to be able to boot systemd in a container.
$ sudo systemd-nspawn -D /chroot/armhf/sid/ -b
I disabled/enabled arm and this confirmed it is the interpreter being
used.
$ sudo update-binfmts --disable qemu-arm
# now fails missing interpreter
Eventually I found I need to unimport it after exchanging the binary.
Then I get it to use the new version.
Note (disable all for some ease to
Hmm, I can recreate the issue myself.
So I thought - yeah onto bisect !
But I fail to get a self built /usr/bin/qemu-arm-static into this.
I wanted to see if 5.1 from git would work and then bisect from there.
But no matter what I try it keeps breaking on the same error.
/me starts to wonder
®Rafael you said you were "able to reproduce LP: #1886811 back then." -
is that true for this bug here as well. It tries to hide from me (fails
before I ever get to it). If you can recreate it maybe we can sync so I
can set up a a git bisect or such.
@Ryutaroh - thanks for the test already.
5.1
@paelzer, I got below. This seems to mean that #LP1887606 is fixed
in 1:4.2-3ubuntu6.4~ppa1 while #LP1890881 remains.
By the way, debian Bullseye 1:5.1+dfsg-0exp1 worked fine as far as I
see.
Preparing to unpack .../qemu-user-static_1%3a4.2-3ubuntu6.4~ppa1_amd64.deb ...
Unpacking
> you could give it a try on focal right?
Yes, I can and I will.
> I'm still unsure what we should do about this bug 1890881 then without
> having an isolated fix, but one step at a time ...
I had a similar feeling: After seeing #LP1886811 fixed in
upstream QEMU, "systemd-nspawn -b" started
So if I could give you a PPA [1] for Focal with the fix for
#LP1887606/#1886811 applied you could give it a try on focal right?
I have added a low prio task for focal to 1886811.
Once tested I'd ask you to:
1. state here if this bug (1890881) is present in focal as well
2. state there (1886811)
Hi @paelzer, what I had done was
testing "netlink RTM_SETLINK command" against the
latest git source of qemu (around July 2020),
and seeing that self-compiled version from the source worked fine.
I had never seen a working Ubuntu qemu-user-static package
that can start an armhf container on an
Thank you both already!
The last fix in git that clearly reads like a fix to this is "65b261a63a
(linux-user: add netlink RTM_SETLINK command" which is already applied.
This also is the latest change to the file, if there is another change
affecting this it must be somewhere else.
Since this is
Hello @emojifrak,
Thanks for reporting this.. I was indeed able to reproduce LP: #1886811
back then.
I'm subscribing @paelzer in this and the other bug...
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606
https://bugs.launchpad.net/qemu/+bug/1886811
** Changed in: qemu (Ubuntu)
** Bug watch added: Debian Bug tracker #968088
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968088
** Also affects: qemu (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968088
Importance: Unknown
Status: Unknown
--
You received this bug notification because
24 matches
Mail list logo
