other: 0.228
semantic: 0.168
graphic: 0.100
device: 0.071
performance: 0.068
files: 0.062
permissions: 0.050
socket: 0.048
network: 0.045
vnc: 0.037
PID: 0.035
debug: 0.032
boot: 0.030
KVM: 0.025
debug: 0.465
other: 0.128
files: 0.072
PID: 0.060
performance: 0.051
network: 0.037
semantic: 0.036
socket: 0.027
boot: 0.024
device: 0.023
permissions: 0.023
KVM: 0.019
vnc: 0.018
graphic: 0.016

[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