blob: e8d2dcb3fafd80832e063b522c6121e2ae2f630b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
id = 2377
title = "Debootstrapping debian-bullseye arm64 segfaults with qemu >=8.1"
state = "opened"
created_at = "2024-06-02T11:10:44.734Z"
closed_at = "n/a"
labels = ["linux-user", "target: arm"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/2377"
host-os = "- Gentoo Linux"
host-arch = "AMD64"
qemu-version = "- 8.1.5, 8.2.3, 9.0.0"
guest-os = "n/a"
guest-arch = "n/a"
description = "n/a"
reproduce = """1. Use qemu >= 8.1 (version <= 8.0.x work well)
2. Install `debootstrap` package
3. Run `sudo debootstrap --arch=arm64 bullseye root11-arm64`
This fails to chroot into the system being debootstrapped:
```
$ sudo debootstrap --arch=arm64 bullseye root11-arm64
...
W: Failure trying to run: chroot "/home/3/root11" /sbin/ldconfig
W: See /home/3/root11/debootstrap/debootstrap.log for details
$ tail -n2 /home/3/root11/debootstrap/debootstrap.log
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
/usr/share/debootstrap/functions: line 1092: 3869 Segmentation fault chroot "/home/3/root11" "$@"
```"""
additional = """Failure happens only when debootstrapping "bullseye" with "arm64" architecture.
Older (e.g. <= "buster") and newer (e.g. > "bookworm") distros are deboostrapped OK.
Other (e.g. "armhf" and others) architectures are debootstrapped OK.
Qemu version <8.1 (e.g. 8.0.5 I use in Gentoo or versions in Debian <= bookworm) don't have the bug.
Originally faced the issue with Gentoo host. Recently rechecked with Debian Trixie host."""
|