Okay, I'm trying to classify this bug report as either user-mode or system-mode. Let me go through the information step by step. The problem is about an SSH connection between a QEMU image (guest) and the host machine running macOS. The issue occurs when the QEMU window is minimized, and after a few minutes, the SSH connection freezes. Clicking back on the QEMU window makes the connection active again. Looking at the details, the user provided their SSH settings from both macOS and Ubuntu Server. They mentioned that the problem seems to be with QEMU. I know that user-mode issues typically involve software running in user space without needing high privileges or device-specific access. System-mode issues usually relate to lower-level components like hardware drivers, kernel operations, or system services. In this case, QEMU is a virtualization application. It interacts with the host's resources and devices, which suggests it might be dealing with lower-level processes. The fact that minimizing QEMU affects the SSH connection could indicate something related to how QEMU handles resources when not in focus—maybe network interfaces or device drivers. Additionally, since the problem persists across different operating systems (macOS as the host and Ubuntu as the guest), it's more likely a system-level issue rather than a user application issue. The interaction between QEMU and the host's networking stack could be causing the SSH connection to drop when the VM is not active. Therefore, I would classify this bug report under 'system' mode because it involves virtualization and resource management at a lower level, which are typically handled in system-mode processes. The issue relates to how QEMU handles network resources when minimized, affecting the SSH connection. This is a low-level process involving device drivers or networking, making it a system-mode problem. system