This bug was fixed in the package qemu - 1:5.0-5ubuntu9.3
---
qemu (1:5.0-5ubuntu9.3) groovy; urgency=medium
* d/p/ubuntu/lp-1907656-s390x-s390-virtio-ccw-Reset-PCI-devices-during-subsy:
avoid PCI devices to become unavailable on reset (LP: #1907656)
* d/rules: fix qemu-user-s
This bug was fixed in the package qemu - 1:5.2+dfsg-3ubuntu1
---
qemu (1:5.2+dfsg-3ubuntu1) hirsute; urgency=medium
* Merge with Debian unstable, includes fixes for
- qemu-user-static are partially dynamically linked (LP: #1908331)
- qemu crashing when using spice without qe
1:5.0-5ubuntu9.2
$ file $(dpkg -L qemu-user-static | grep bin\/qemu-.*-static)
...
/usr/bin/qemu-xtensaeb-static: ELF 64-bit LSB shared object, x86-64,
version 1 (GNU/Linux), dynamically linked,
BuildID[sha1]=99dc333d7f8a78620600e5807de92b60dba54468, for GNU/Linux 3.2.0,
stripped
1:5.0-5ub
Hello TJ, or anyone else affected,
Accepted qemu into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:5.0-5ubuntu9.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubun
Review and pre-tests ok, uploaded to 21.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-user-static binaries are dynamically linked
To manage notifications about th
Uploaded and ready for the review by the SRU Team
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-user-static binaries are dynamically linked
To manage notifications a
SRU prepared (template in bug description) and tested against the PPA
(https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4389) and
reviewed
(https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/395786).
I will upload that to -unapproved soon
--
You received this bug
** Description changed:
- On 20.04 (qemu 4.2) the binaries built for qemu-user-static -
- specifically in the case I've hit /usr/bin/qemu-aarch64-static - are
- completely static executables.
+ [ Impact ]
+
+ * An upstream change [1] had undesired impact of making qemu-user-static
+no more
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/395786
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-user-stati
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: qemu (Ubuntu Groovy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Reg
My change was accepted upstream and in 5.2-3 - I'll merge that in the
coming days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-user-static binaries are dynamically
Now that root-cause and solution is rather clear I have submitted that to
Debian (which is affected the same way).
But I will personally enter the EOY-downtime before I can fix it in an Ubuntu
upload - OTOH this isn't super urgent I guess - and if my prio-assumption is
wrong the fix is available
Bisect agrees
$ git bisect log
git bisect start
# old: [b0ca999a43a22b38158a33d3f5881648bb4f] Update version for v4.2.0
release
git bisect old b0ca999a43a22b38158a33d3f5881648bb4f
# new: [fdd76fecdde1ad444ff4deb7f1c4f7e4a1ef97d6] Update version for v5.0.0
release
git bisect new fdd76fecd
Building v5.0.0 with --disable-pie:
flags now are:
QEMU_LDFLAGS -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static -m64
-fstack-protector-strong
And the file is as we'd like it to be:
./aarch64-linux-user/qemu-aarch64: ELF 64-bit LSB executable, x86-64, version 1
(GNU/Linux), statically
Just looking at git history maybe
https://git.qemu.org/?p=qemu.git;a=commit;h=127814629b32d5e0de2873d742e08cb9bd412af7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-u
Confirmed to recreate from git as well:
v5.0.0
./aarch64-linux-user/qemu-aarch64: ELF 64-bit LSB shared object, x86-64,
version 1 (GNU/Linux), dynamically linked,
BuildID[sha1]=1521984faacf9472c1df8fe37c2a0fb5e2f55aba, for GNU/Linux 3.2.0,
with debug_info, not stripped
v4.2.0
./aarch64-linux-u
Thanks for the great report TJ.
Indeed configure --static converts to
4.2
LDFLAGS -Wl,--warn-common -m64 -static -g -Wl,-Bsymbolic-functions
-Wl,-z,relro -Wl,--as-needed
QEMU_LDFLAGS···
5.0
QEMU_LDFLAGS -Wl,--warn-common -Wl,-z,relro -Wl,-z,now -static-pie -m64
-g -O2 -fde
If -static-pie is indeed impoartant here - it is rather new and had problems
before.
An excerpt from d/rules:
114 ifneq ($(filter $(DEB_HOST_ARCH),i386 x32),)
115 # XXX as of 2020-04-29, i386 buildd fails to link -static-pie executable:
116 # /usr/b
I've posted a question to the qemu-devel mailing list with subject "Are
user static builds really dynamically linked ?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908331
Title:
Regression: qemu-
To be sure I built upstream v4.2.1 and it reports the expected and
required linkage. Build needs some additional tweaking to avoid libssh
deprecated functions causing -Werror to trigger:
$ sudo apt install liblzma-dev
$ ../../qemu/configure --target-list=aarch64-linux-user --static
--disable-syst
** Description changed:
On 20.04 (qemu 4.2) the binaries built for qemu-user-static -
specifically in the case I've hit /usr/bin/qemu-aarch64-static - are
completely static executables.
The same binaries from a qemu 5.x build are not. Although they don't
link to other shared libraries
21 matches
Mail list logo
