blob: 08b205cf8768bc4c28d28af6a52993f3f3195141 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
mistranslation: 0.589
other: 0.499
graphic: 0.384
semantic: 0.340
device: 0.266
socket: 0.193
network: 0.165
instruction: 0.122
vnc: 0.109
boot: 0.104
KVM: 0.056
assembly: 0.031
[RFE] option to suppress gemu_log() output
With user mode emulation, messages from genu_log() are emitted unconditionally to stderr. I didn't find a way to suppress them. It would be nice to have options similar to the -D/-d options to be able to filter and/or redirect the output.
My use case is chroot/container execution for different architectures via binfmt. In this case it will appear as if the binary in question had emitted messages like "Unsupported setsockopt ..." to stderr while in fact the message came from qemu-*-static.
This series might be helpful:
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02067.html
The -d/-D options should work in linux-user as well. You can also set QEMU_LOG_FILENAME and QEMU_LOG environment variables. Do these not work for you?
Although arguably the line:
gemu_log("Unsupported setsockopt level=%d optname=%d\n", level, optname);
Could be
qemu_log_mask(LOG_UNIMP,....)
Not sure where gemu_log is used, it seems to be strace related.
Indeed I think gemu_log() is the problem here.
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/171
|