Alright, let me try to figure out how to classify this bug report. The user is experiencing an issue where they're getting "Function not implemented" errors when using the Linux libaio library within a Docker container that's emulating an aarch64 architecture via QEMU. Looking at the steps provided: 1. They set up QEMU for static binaries. 2. Run a Docker image with arm64v8/centos:8. 3. Install GCC and libaio inside the container. 4. Compile a simple C program that uses libaio functions. The problem occurs when running this program in the emulated environment, where it returns res = -38 (ENOSYS), which means the function isn't implemented. However, it works fine on native aarch64 and x86_64 without emulation. I know that ENOSYS is returned when a system call isn't implemented by the kernel. So, in this case, the QEMU user-mode emulation might not be handling some syscalls correctly for the arm64 architecture. The user tried using strace but got similar errors about ptrace functions not being implemented. This suggests that certain syscalls are missing or not properly handled in the emulated environment. So, the issue revolves around system calls not being implemented when running under QEMU's emulation, specifically for libaio which relies on specific syscalls like io_queue_init. Therefore, this seems to be a problem related to how QEMU handles these particular syscalls during emulation. Thus, the category should be "syscall" because it's an error occurring with system calls in the emulated environment. The bug report involves issues with system calls not being implemented correctly under QEMU's user-mode emulation. The ENOSYS error indicates that certain syscalls aren't handled, which is related to how QEMU processes these calls for different architectures. **Answer:** syscall