blob: 2db2232cd8c94b2d091f309a1d293b438d15ec9b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to figure out whether this bug is related to user-mode or system-mode in QEMU based on the provided information.
The problem occurs when running `qemu-arm` with a minimal Debian install that includes SSH. The error message is "Allocating guest commpage: Cannot allocate memory" when executing `systemctl --version`.
From the steps to reproduce, the user compiles QEMU with specific flags for arm-linux-user and runs it in user mode since `-L ./` points to a directory containing the necessary libraries and executables. The fact that adding `-B 0x20000` fixes the issue suggests a memory allocation problem within the user-mode environment, possibly related to how QEMU maps or manages memory for the guest process.
The mention of Issue 690 on GitLab points to a known issue where certain allocations in user mode could fail due to memory constraints. The change in behavior between QEMU versions (working in 5.0.0 but not in later versions) indicates this might be related to how memory management was altered, affecting user-mode processes.
Since the error is encountered when running a command (`systemctl`) through QEMU's user emulator without involving system-level components like device emulation or full OS virtualization, it points towards a user-mode issue. The system-mode would typically involve more comprehensive setups with hardware devices and higher privileges, which isn't the case here.
Therefore, this bug is likely related to user-mode operations in QEMU.
</think>
user
|