This bug was fixed in the package linux-raspi - 6.8.0-1007.7
---
linux-raspi (6.8.0-1007.7) noble; urgency=medium
* noble/linux-raspi: 6.8.0-1007.7 -proposed tracker (LP: #2068311)
* Cannot launch armhf containers on arm64 host under noble (LP: #2062176)
- [Config] raspi: Rev
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2006.6 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-noble-linux-raspi-realtime'
to 'verification-done-noble-li
Verification for Noble of linux-image-6.8.0-1007-raspi:
root@ubuntu:~# apt-get dist-upgrade -V -t noble-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
linux-
This bug is awaiting verification that the linux-raspi/6.8.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-raspi' to 'verification-done-noble-
linux-raspi'. If the
Any update on this? Or is there a way to get the 1001 kernel back until
it's fixed? (apt apparently deleted it on me)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
Cannot launch armhf
I'll turn it back on for raspi. The others are cloud kernels. I'll talk
to the respective kernel owners to figure this out with the cloud
vendors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
I think the consensus at this point is that, while this manifests in LXD
(and chroot), it's ultimately a kernel configuration issue. Marking lxd
invalid.
Just to fill in a bit of background, there's been some discussion
between kernel team and foundations what the correct course of action
here is
Another reproducer:
# cat test2.c
#include
#include
void *threadfn(void *ptr)
{
return NULL;
}
int main(int argc, char **argv)
{
pthread_t thread;
pthread_create(&thread, NULL, &threadfn, NULL);
pthread_join(thread, NULL);
return 0;
}
# arm-linux-gnueabihf-gcc -D_FILE_OFF
** Description changed:
+ [Impact]
+
Under the current noble daily server image for Raspberry Pi (arm64
architecture) I cannot launch an armhf container image using lxd from
the channel 5.21/stable/ubuntu-24.04 (build 28284). It *appears* to
launch successfully, and lxd reports no error y
>The test case given in the github issue is invalid, because it builds
without the default noble compiler flags of -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 so tells us nothing about what code is actually being
run as part of noble that depends on the old syscall.
It's not invalid, cause we can't req
Hi Steve,
I have described a reason of this issue above:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2062176/comments/3
>So this is not a bug in glibc,
This is not a bug. This is a kernel configuration issue.
Kernel configuration has COMPAT_32BIT_TIME=n, but must have COMPAT_32BIT_TIME=y
I initially reassigned this from lxd to glibc on the basis that glibc is
responsible for deciding whether to use the 64-bit vs 32-bit time_t
variants for all the syscalls it wraps, and give preference to the
64-bit variants; HOWEVER,
Note: glibc provides no wrapper for futex(), necessitat
** Package changed: lxd (Ubuntu) => glibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
Cannot launch armhf containers on arm64 host under noble
To manage notifications abou
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
Cannot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-raspi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
** Changed in: lxd
Status: New => 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/2062176
Title:
Cannot launch armhf containers on arm64 host under noble
To manage notifications a
This is the reason:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/noble/tree/debian.raspi/config/annotations?h=master-next#n155
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038582
Minimal reproducer:
# cat test.c
#define _GNU_SOURCE
#include
#include
#includ
** Tags added: kern-10956
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
Cannot launch armhf containers on arm64 host under noble
To manage notifications about this bug go to:
https:/
** Changed in: lxd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062176
Title:
Cannot launch armhf containers on arm64 host under noble
To manage notifications about
As I could reproduce the issue I opened
https://github.com/canonical/lxd/issues/13512 to track it.
Thanks Dave for bringing this to our attention.
** Bug watch added: github.com/canonical/lxd/issues #13512
https://github.com/canonical/lxd/issues/13512
** Also affects: lxd via
https://githu
This is likely to be a linux-raspi issue since armhf containers are
apparently working happily in the autopkgtest cloud. Further, armhf
chroots are also failing under linux-raspi with a Futex error from the
kernel (will attempt to add some detail on this in due course).
** Also affects: linux-rasp
21 matches
Mail list logo
