summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/hypervisor/2377
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/hypervisor/2377
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/hypervisor/2377')
-rw-r--r--results/classifier/gemma3:12b/hypervisor/237726
1 files changed, 26 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/hypervisor/2377 b/results/classifier/gemma3:12b/hypervisor/2377
new file mode 100644
index 000000000..4928078f7
--- /dev/null
+++ b/results/classifier/gemma3:12b/hypervisor/2377
@@ -0,0 +1,26 @@
+
+Debootstrapping debian-bullseye arm64 segfaults with qemu >=8.1
+Steps to 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 information:
+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.