Okay, so I'm trying to figure out what category this bug report falls under. The user mentioned they're using QEMU inside a Docker container on a Raspberry Pi 4 with ESXi hypervisor. They're getting an error where QEMU is receiving a signal outside the vCPU context. First, looking at the error message: "handle_cpu_signal received signal outside vCPU context." This suggests that there's some kind of runtime issue within QEMU when handling signals, specifically not in the virtual CPU context. Signals are part of how processes communicate and handle events, like interruptions or errors. So this isn't about a specific instruction being wrong (instruction category) nor is it directly related to system calls (syscall). Instead, it's something that happens while the program is running. The user provided their QEMU version as 5.1.0 from Debian. The error seems to occur during execution when handling signals outside the expected context, which points towards a runtime problem. So, I think this falls under the 'runtime' category because it's an issue that occurs while the software is executing, not during instruction processing or system calls. The error is related to how QEMU handles signals at runtime, specifically outside the virtual CPU context, indicating a runtime issue. runtime