blob: 13941e59c1f7acfeae1c94f16f1d49e5a99e9b32 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
|
<think>
Okay, let's see. The user is reporting an issue with QEMU where the memfd_create syscall isn't supported in user mode. The error message says "qemu: Unsupported syscall: 319".
First, I need to figure out what category this falls into. The options are instruction, syscall, or runtime. The problem here is that QEMU doesn't implement the memfd_create syscall, which is a system call. The error message specifically mentions an unsupported syscall, so it's directly related to syscall handling.
The user mentions that the application requires memfd_create and QEMU is failing because it doesn't support it. That's a missing syscall implementation in QEMU's user mode. So the correct category should be 'syscall' because the issue is about a system call not being supported. It's not an instruction error or a general runtime error, but specifically a missing syscall handler.
</think>
syscall
|