1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I need to figure out whether this bug in QEMU is related to user-mode or system-mode. The user reported that after updating to version 8.1.1, running ldconfig using qemu-aarch64-static causes a crash (segfault).
First, let me understand what's happening here. They're using qemu-aarch64-static to run an arm64 binary, specifically ldconfig.real, in their sysroot which is a Ubuntu 22.04 rootfs. Before the update to 8.1.1, it worked fine with version 8.1.0.
So, QEMU can emulate different architectures, and qemu-aarch64-static is for running AArch64 binaries in user mode. User-mode emulation typically involves executing applications without full OS virtualization. In this case, they're using the '-r' option to rootfs, which I think is setting up a chroot environment or similar, but still within user space.
The crash occurs when ldconfig runs, which suggests that the issue might be with how QEMU is handling system calls or binaries in user mode. Since it's crashing during execution of a tool that configures shared libraries (ldconfig), maybe there's an issue with how dynamic linking or shared library resolution is being handled under the emulator.
System-mode issues usually involve higher-level privileges, device emulation, or full OS virtualization. But here, they're just running a single command inside the emulator without booting an entire system, so it seems more like a user-mode problem.
Another point: They're using qemu-aarch64-static, which is specifically for static user-mode execution. So this points towards a user-mode issue rather than something related to virtualizing an entire OS or hardware devices.
So putting it all together, the bug report relates to QEMU's user-mode functionality when running specific binaries, leading to a segfault. Therefore, it should be classified as 'user' mode.
</think>
user
|