1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, so I'm trying to figure out whether this QEMU issue is a user-mode or system-mode problem. Let's break it down.
The user mentioned that when they run an armv7 qemu chroot on their x86_64 desktop, they get repeated messages saying "qemu: Unsupported syscall: 384". They provided some context from an IRC chat where someone suggested that this is related to the sys_getrandom system call. The user also noted that this wasn't a problem before and that it's been about six months since they used this environment, with many package updates in between.
First, I need to understand what each term means. QEMU has two main modes: user-mode emulation and system-mode emulation. User-mode is for running individual programs without an entire OS, while system-mode runs a full OS, handling things like hardware devices and higher privileges.
In this case, the issue arises when compiling inside the chroot environment using qemu-linux-user-2.9.0. The error message points to an unsupported syscall (number 384), which is getrandom. From what I know, sys_getrandom is a system call used for generating random numbers securely. If QEMU doesn't support it, applications trying to use this might fall back to /dev/urandom, as the IRC chat suggested.
Since the user is using qemu-linux-user, that's part of the user-mode setup because they're running an armv7 chroot on x86_64 without a full OS layer. The problem occurs when compiling (a userspace activity), and it's about handling a system call that's not implemented in QEMU's user-mode emulation.
So, this seems to be related to how QEMU handles user-space processes and their syscalls. Since getrandom is a standard syscall that applications might use, the fact that QEMU doesn't support it would fall under user-mode issues because it's about running binaries correctly without a full OS context.
Therefore, I think this bug report should be classified as 'user' mode related.
</think>
The issue involves an unsupported system call (getrandom) encountered while using QEMU in user-mode to run armv7 binaries on x86_64. This pertains to how user-space applications interact with the emulation.
user
|