From: Laurent Vivier <1922617@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1922617] Re: qemu-aarch64-static "Illegal instruction" with debootstrap
Date: Tue, 06 Apr 2021 13:51:02 -0000 [thread overview]
Message-ID: <161771706219.17322.9097877401738993351.malone@soybean.canonical.com> (raw)
In-Reply-To: 161767088471.29958.926730188235259416.malonedeb@gac.canonical.com
Bisected to
commit 26bab757d41b853ea84cb52a10fafc9c10069658
Author: Richard Henderson <richard.henderson@linaro.org>
Date: Fri Feb 12 10:48:33 2021 -0800
linux-user: Introduce PAGE_ANON
Record whether the backing page is anonymous, or if it has file
backing. This will allow us to get close to the Linux AArch64
ABI for MTE, which allows tag memory only on ram-backed VMAs.
The real ABI allows tag memory on files, when those files are
on ram-backed filesystems, such as tmpfs. We will not be able
to implement that in QEMU linux-user.
Thankfully, anonymous memory for malloc arenas is the primary
consumer of this feature, so this restricted version should
still be of use.
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Message-id: 20210212184902.1251044-3-richard.henderson@linaro.org
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1922617
Title:
qemu-aarch64-static "Illegal instruction" with debootstrap
Status in QEMU:
New
Bug description:
This is reproducible against QEMU master. I apologize for the long
reproduction steps, I tried to distill it down as much as possible.
System info:
# qemu-aarch64-static --version
qemu-aarch64 version 5.2.91 (v6.0.0-rc1-68-gee82c086ba)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
# head -n 26 /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 85
model name : Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz
stepping : 7
microcode : 0x5002f01
cpu MHz : 1000.716
cache size : 22528 KB
physical id : 0
siblings : 32
core id : 0
cpu cores : 16
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single intel_ppin ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke avx512_vnni md_clear flush_l1d arch_capabilities
bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit
bogomips : 4600.00
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
My reproduction steps:
# apt-get install --no-install-recommends -y \
build-essential \
ca-certificates \
debootstrap \
git \
libglib2.0-dev \
libpixman-1-dev \
ninja-build \
pkg-config \
python3 \
zstd
# git clone https://github.com/qemu/qemu
# mkdir qemu/build
# cd qemu/build
# ../configure \
--enable-debug \
--enable-linux-user \
--disable-bsd-user \
--disable-werror \
--disable-system \
--disable-tools \
--disable-docs \
--disable-gtk \
--disable-gnutls \
--disable-nettle \
--disable-gcrypt \
--disable-glusterfs \
--disable-libnfs \
--disable-libiscsi \
--disable-vnc \
--disable-kvm \
--disable-libssh \
--disable-libxml2 \
--disable-vde \
--disable-sdl \
--disable-opengl \
--disable-xen \
--disable-fdt \
--disable-vhost-net \
--disable-vhost-crypto \
--disable-vhost-user \
--disable-vhost-vsock \
--disable-vhost-scsi \
--disable-tpm \
--disable-qom-cast-debug \
--disable-capstone \
--disable-zstd \
--disable-linux-io-uring \
--static \
--target-list-exclude=hexagon-linux-user
# ninja qemu-aarch64
# install -Dm755 qemu-aarch64 /usr/local/bin/qemu-aarch64-static
# cat <<'EOF' >/proc/sys/fs/binfmt_misc/register
:qemu-aarch64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\xb7:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff:/usr/local/bin/qemu-aarch64-static:CF
EOF
# debootstrap --arch arm64 --foreign buster debian-rootfs
# chroot debian-rootfs /debootstrap/debootstrap --second-stage
Illegal instruction
This prevents me from building an arm64 Debian image on x86_64. If I
am doing something wrong, please let me know. The binary has been
uploaded for your convenience.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1922617/+subscriptions
next prev parent reply other threads:[~2021-04-06 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 1:01 [Bug 1922617] [NEW] qemu-aarch64-static "Illegal instruction" with debootstrap Nathan Chancellor
2021-04-06 9:33 ` [Bug 1922617] " Peter Maydell
2021-04-06 10:22 ` Laurent Vivier
2021-04-06 10:47 ` Laurent Vivier
2021-04-06 13:51 ` Laurent Vivier [this message]
2021-04-06 15:05 ` Philippe Mathieu-Daudé
2021-04-06 15:28 ` Richard Henderson
2021-04-06 15:55 ` Laurent Vivier
2021-04-06 16:29 ` Laurent Vivier
2021-04-06 16:32 ` Laurent Vivier
2021-04-06 17:06 ` Richard Henderson
2021-04-13 0:25 ` Richard Henderson
2021-04-30 8:22 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161771706219.17322.9097877401738993351.malone@soybean.canonical.com \
--to=1922617@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).