blob: 4d043dfb3df3f64b39a9c462485cd4357af899f4 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, I need to classify this bug report as either user-mode or system-mode. Let's break it down.
The issue is happening when trying to run a bare chroot using QEMU. The error message mentions pgb_reserved_va and an assertion failure where guest_base isn't zero. This suggests something related to memory management within the emulated environment.
The workaround involves bind-mounting /proc, which is a system-level operation but doesn't directly indicate mode. However, the fact that it's a chroot and using QEMU in user-mode implies that the problem is within user-mode emulation.
Additionally, the bug report specifically mentions the 'linux-user' component of QEMU, which handles user-mode execution without a full OS. This points towards a user-mode issue rather than something involving system hardware or higher privileges.
So, considering all this, the bug seems to be in the user-mode part of QEMU.
</think>
user
|