aarch64 container problem on x86_64

[zebul666]

I had a rpi aarch64 systemd-nspawn container on x86_64

And I now I can't even get a prompt when I run [code]systemd-nspawn --bind-ro /etc/resolv.conf -M sinope -D archlinuxARM-aarch64-sinope[/code]

It also happened with an arm7 rpi container.

When I use arch-chroot instead. the terminal is not workiing properly where tab or uparrow does not work in bash.
tmux and other tty related comand are broken (like less)

I can now reproduce the problem by downloading the latest ArchlinuxARM-rpi-aarch64-latest.tar.gz from today 2025-11-10.
If I use it like that it's ok. But if I run [code]pacman -Syu[/code] in the container, and exit it. I can't re enter because I never get a prompt on the next systemd-nspawn.

I tried to downagrade systemd, binutils. But this changed nothing.

All I can say if something is broken after upgrading:

[code]binutils 2.44-1 -> 2.45+r29+g2b2e51a31ec7-1
curl 8.16.0-1 -> 8.17.0-1
device-mapper 2.03.36-1 -> 2.03.36-2
glib2 2.86.1-1 -> 2.86.1-1.1
glibc 2.41+r6+gcf88351b685d-1 -> 2.42+r17+gd7274d718e6f-1
hwdata 0.400-1 -> 0.401-1
iana-etc 20250612-1 -> 20251030-1
libelf 0.194-1 -> 0.194-1.1
libsysprof-capture 49.0-1 -> 49.0-1.1
libxcrypt 4.4.38-1 -> 4.5.1-1
linux-aarch64 6.17.7-2 -> 6.17.7-3
mkinitcpio 39.2-5 -> 40-1
raspberrypi-bootloader 20251031-1 -> 20251104-1
sqlite 3.50.4-2 -> 3.51.0-1
systemd 258.1-1 -> 258.2-1
systemd-libs 258.1-1 -> 258.2-1
systemd-resolvconf 258.1-1 -> 258.2-1
systemd-sysvcompat 258.1-1 -> 258.2-1[/code]

The containers are not booted (no -b)

[neo1973]

I can confirm the problem with an armv7h rpi container as well.

The problems seems to be glibc, if I update everything except glibc (keep version 2.41+r6+gcf88351b685d-1) the problem doesn't occur.

[neo1973]

Ahh, it looks like the problem is actually with qemu:make_clickable_callback(MAGIC_URL_FULL, ' ', 'https://gitlab.com/qemu-project/qemu/-/issues/3065', '', ' class="postlink"')

[zebul666]

thanks to let us know.

So there is no point in downgrading qemu, because the missing feature still woulnd't be there, right?

[neo1973]

That's correct. There is a little activity on the mailing list regarding this topic but progress seems to be slow. Lets hope that this is implemented by the end of the year.

[graysky]

My first time using systemd-nspawn but I am seeing no such problems running aarch64.

systemd-nspawn -D /var/lib/machines/arm64-container /bin/bash

[neo1973]

Previously I tried "arch-chroot -S" which also uses systemd-nspawn. But never the less the command tty says "not a tty", top says "top: failed tty get" and problems like that. Using systemd-nspawn directly has the same problem.

The system is still usable to some degree but the lack of an interactive shell makes things very difficult.

[zebul666]

yes, I am using arch-chroot as a fallback, but it is less than ideal, with some command broken, and the shell hard to use interactively
arch-chroot use chroot, right?

@graysky; we are a least 2 to get the problem. Do you run an arm64 host machine ? What is your glibc guest version? I don't know why you don't see the problem.
arch-chroot has the same problem. not the same symptoms

[graysky]

Ah, not x86_64 host/aarch64 container.