blob: cbe9d035bc00e72438c38694106e5d81d8c46999 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to classify this bug report as either 'user-mode' or 'system-mode'. Let's break it down.
The user is using QEMU with an arm chroot on an amd64 host, specifically the command "qemu-user arm cortex-a8". That makes me think they're using user-mode emulation because qemu-user is for running binaries of another architecture without a full VM. They mention building coreutils hangs during a specific check related to memory limits.
The issue seems to be with the guest's memory ulimit being too small, which affects how the build process runs. Since they are emulating an arm environment on amd64 using user-mode QEMU, it's more about the application-level issues rather than system-level stuff like hardware or full OS emulation.
They're not mentioning anything about virtual machines or device emulation beyond the CPU, so it doesn't sound like system-mode which would involve higher privileges or peripherals. It's more about how the userland processes are handling memory constraints within the emulated environment.
So putting it all together, this bug is related to user-mode because it deals with running applications and their resource limits in an emulated user space.
</think>
user
|