blob: ec0a63d005fadf070e6a987d254fe29d2c6f2f44 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I have this bug report about QEMU where someone is having issues with gemu_log() messages appearing in stderr when they run user mode emulation. They want a way to suppress these messages, similar to how -D/-d options work for filtering or redirecting output.
The user's specific case is using chroot or containers with binfmt support for different architectures. When they do this, the binary seems to emit messages like "Unsupported setsockopt..." which actually come from QEMU-static. This can be confusing because it looks like the application itself is logging these errors, but it's really QEMU doing so.
I need to classify this bug as either 'user-mode' or 'system-mode'. System-mode issues usually involve higher privileges, peripherals, devices, and operating systems. Since this report is about messages from gemu_log() in user mode emulation, it seems related to how user-mode processes interact with logging.
So, the issue here is about controlling log output in user-mode QEMU. The fact that these logs are appearing when running applications within a chroot or container using binfmt suggests it's definitely in user space and not dealing with kernel-level devices or higher privileges.
Therefore, I think this bug report falls under 'user' mode.
</think>
The issue is related to the logging output in user-mode QEMU, which affects how messages are displayed when running applications in a chroot or container environment. This doesn't involve system-level components but rather the behavior of user-mode processes and their logs.
user
|