[Bug 2062176] Re: Cannot launch armhf containers on arm64 host under noble

[Steve Langasek]

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(), necessitating the use of
       syscall(2).

futex(2).

Confirmed that there are no 'futex' symbols in glibc.

So this is not a bug in glibc, and there is insufficient information
here or in the linked github issue to say where the problem lies.  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.

Someone will need to strace this to find the guilty binary.

** Package changed: glibc (Ubuntu) => lxd (Ubuntu)

** Changed in: lxd (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2062176

Title:
  Cannot launch armhf containers on arm64 host under noble

Status in lxd:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Incomplete

Bug description:
  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 yet afterward the
  container is stopped:

  $ lxc launch ubuntu-daily:n/armhf nobletest
  Creating nobletest
  Starting nobletest
  $ lxc list
  +-----------+---------+------+------+-----------+-----------+
  |    NAME   |  STATE  | IPV4 | IPV6 |   TYPE    | SNAPSHOTS |
  +-----------+---------+------+------+-----------+-----------+
  | nobletest | STOPPED |      |      | CONTAINER | 0         |
  +-----------+---------+------+------+-----------+-----------+

  In case this was an issue with the current noble daily, I also
  attempted launching the mantic and jammy armhf images, but with the
  same symptoms:

  $ lxc launch ubuntu:m/armhf mantictest
  Creating mantictest
  Starting mantictest
  $ lxc list
  +------------+---------+------+------+-----------+-----------+
  |    NAME    |  STATE  | IPV4 | IPV6 |   TYPE    | SNAPSHOTS |
  +------------+---------+------+------+-----------+-----------+
  | nobletest  | STOPPED |      |      | CONTAINER | 0         |
  +------------+---------+------+------+-----------+-----------+
  | mantictest | STOPPED |      |      | CONTAINER | 0         |
  +------------+---------+------+------+-----------+-----------+

  I attempted the same tests under the 23.10 server for Pi images (also
  arm64 host) and both containers launched successfully, so this appears
  to be an issue with lxd under noble specifically.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lxd/+bug/2062176/+subscriptions