From: "Philippe Mathieu-Daudé" <1828723@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1828723] Re: [RFE] option to suppress gemu_log() output
Date: Mon, 08 Jul 2019 16:52:56 -0000 [thread overview]
Message-ID: <156260477688.24806.14082885607056565648.malone@soybean.canonical.com> (raw)
In-Reply-To: 155766144999.15801.8727893741494500797.malonedeb@wampee.canonical.com
This series might be helpful:
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02067.html
** Tags added: linux-user
--
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:
New
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
next prev parent reply other threads:[~2019-07-08 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 11:44 [Qemu-devel] [Bug 1828723] [NEW] [RFE] option to suppress gemu_log() output Thomas Moschny
2019-07-08 16:52 ` Philippe Mathieu-Daudé [this message]
2019-07-17 15:08 ` [Qemu-devel] [Bug 1828723] " Alex Bennée
2019-07-17 15:10 ` Alex Bennée
2019-07-18 21:32 ` Thomas Moschny
2021-05-05 11:28 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=156260477688.24806.14082885607056565648.malone@soybean.canonical.com \
--to=1828723@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.