blob: 2ee52d564d08f1b7ab23673d704cb99e75f58e45 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to figure out how to classify this bug report related to QEMU. The user provided some details about an error they encountered when running qemu-i386-static. Let me go through the problem step by step.
First, looking at the error message: "Unable to reserve 0xfffff000 bytes of virtual address space at 0x1000 (Operation not supported)". This suggests that QEMU is trying to map a large chunk of memory but isn't allowed to do so. The strace output shows an mmap call with MAP_FIXED_NOREPLACE returning EOPNOTSUPP, which means the operation isn't supported.
The user mentions they're running on a kernel version 4.4, and that QEMU is checking for MAP_FIXED_NOREPLACE at build-time but not at runtime. They suspect that detecting this feature at runtime could solve the issue because the kernel doesn't support it here.
So, looking at the possible categories: instruction, syscall, or runtime. The problem isn't about a faulty instruction in the code (instruction category) nor is it an error directly with a system call (syscall). It's more about how QEMU handles the availability of certain memory mapping features during execution. Since QEMU is trying to use MAP_FIXED_NOREPLACE but the kernel doesn't support it, and this detection only happens at build-time, the issue arises during runtime when the feature isn't present.
Therefore, the bug report is about a runtime error because it's occurring while the program is running, not due to an incorrect instruction or a problem with a specific system call itself.
</think>
runtime
|