[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1828723] Re: [RFE] option to suppress gemu_log() output
From: |
Thomas Huth |
Subject: |
[Bug 1828723] Re: [RFE] option to suppress gemu_log() output |
Date: |
Wed, 05 May 2021 11:28:16 -0000 |
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
** Changed in: qemu
Status: New => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #171
https://gitlab.com/qemu-project/qemu/-/issues/171
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828723
Title:
[RFE] option to suppress gemu_log() output
Status in QEMU:
Expired
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1828723/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1828723] Re: [RFE] option to suppress gemu_log() output,
Thomas Huth <=