From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Markus Armbruster <armbru@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 19:48:30 +0300 [thread overview]
Message-ID: <4C4F0DDE.4000004@redhat.com> (raw)
In-Reply-To: <4C4F0D9F.1030903@redhat.com>
On 07/27/2010 07:47 PM, Avi Kivity wrote:
> On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
>>
>>> I read that to mean...propagate stderr from qemu to be right in
>>> front of
>>> the user. So that's output from virsh or in virt-manager. Trouble is,
>>> that's only useful (at best) when starting a guest. Perhaps some
>>> virt-manager thing (an exclamation point to show there's errors in the
>>> log and a way to read them), and a virsh utility to match (although
>>> that'd require the user to actually poll the interface, at which point
>>> they can just as easily just look at the log).
>> We already propagate the stderr back to the client when guest startup
>> fails.
>
> I'm talking about when it doesn't fail, just spews out some warnings.
>
Note, it needn't be during startup. If qemu says something while the
guest is running, we need to get it to bugzilla, just like a kernel
WARN_ON() or BUG_ON() will make it to kerneloops.org.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 19:48:30 +0300 [thread overview]
Message-ID: <4C4F0DDE.4000004@redhat.com> (raw)
In-Reply-To: <4C4F0D9F.1030903@redhat.com>
On 07/27/2010 07:47 PM, Avi Kivity wrote:
> On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
>>
>>> I read that to mean...propagate stderr from qemu to be right in
>>> front of
>>> the user. So that's output from virsh or in virt-manager. Trouble is,
>>> that's only useful (at best) when starting a guest. Perhaps some
>>> virt-manager thing (an exclamation point to show there's errors in the
>>> log and a way to read them), and a virsh utility to match (although
>>> that'd require the user to actually poll the interface, at which point
>>> they can just as easily just look at the log).
>> We already propagate the stderr back to the client when guest startup
>> fails.
>
> I'm talking about when it doesn't fail, just spews out some warnings.
>
Note, it needn't be during startup. If qemu says something while the
guest is running, we need to get it to bugzilla, just like a kernel
WARN_ON() or BUG_ON() will make it to kerneloops.org.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-27 16:48 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:28 KVM call agenda for July 27 Chris Wright
2010-07-26 21:28 ` [Qemu-devel] " Chris Wright
2010-07-26 22:28 ` Anthony Liguori
2010-07-26 22:28 ` [Qemu-devel] " Anthony Liguori
2010-07-26 23:28 ` Anthony Liguori
2010-07-26 23:28 ` [Qemu-devel] " Anthony Liguori
2010-07-27 0:13 ` Alex Williamson
2010-07-27 0:13 ` [Qemu-devel] " Alex Williamson
2010-07-27 13:22 ` Jes Sorensen
2010-07-27 13:22 ` [Qemu-devel] " Jes Sorensen
2010-07-27 7:19 ` Markus Armbruster
2010-07-27 7:19 ` [Qemu-devel] " Markus Armbruster
2010-07-27 13:00 ` Anthony Liguori
2010-07-27 13:00 ` [Qemu-devel] " Anthony Liguori
2010-07-27 13:28 ` Kevin Wolf
2010-07-27 13:28 ` Kevin Wolf
2010-07-27 15:22 ` Markus Armbruster
2010-07-27 15:22 ` Markus Armbruster
2010-07-27 15:28 ` Anthony Liguori
2010-07-27 15:28 ` Anthony Liguori
2010-07-27 15:37 ` Daniel P. Berrange
2010-07-27 15:37 ` Daniel P. Berrange
2010-07-27 16:17 ` Avi Kivity
2010-07-27 16:17 ` Avi Kivity
2010-07-27 16:24 ` Daniel P. Berrange
2010-07-27 16:24 ` Daniel P. Berrange
2010-07-27 16:29 ` Chris Wright
2010-07-27 16:29 ` Chris Wright
2010-07-27 16:32 ` Avi Kivity
2010-07-27 16:32 ` Avi Kivity
2010-07-27 16:36 ` Chris Wright
2010-07-27 16:36 ` Chris Wright
2010-07-27 16:42 ` Avi Kivity
2010-07-27 16:42 ` Avi Kivity
2010-07-27 17:01 ` Daniel P. Berrange
2010-07-27 17:01 ` Daniel P. Berrange
2010-07-27 17:37 ` Avi Kivity
2010-07-27 17:37 ` Avi Kivity
2010-07-27 16:42 ` Daniel P. Berrange
2010-07-27 16:42 ` Daniel P. Berrange
2010-07-27 16:47 ` Avi Kivity
2010-07-27 16:47 ` Avi Kivity
2010-07-27 16:48 ` Avi Kivity [this message]
2010-07-27 16:48 ` Avi Kivity
2010-07-28 11:22 ` Markus Armbruster
2010-07-28 11:25 ` Kevin Wolf
2010-07-28 11:25 ` Kevin Wolf
2010-07-28 13:08 ` Markus Armbruster
2010-07-27 11:51 ` Daniel P. Berrange
2010-07-27 11:51 ` [Qemu-devel] " Daniel P. Berrange
2010-07-27 13:30 ` Anthony Liguori
2010-07-27 13:30 ` [Qemu-devel] " Anthony Liguori
2010-07-27 13:43 ` Cole Robinson
2010-07-27 13:43 ` [Qemu-devel] " Cole Robinson
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=4C4F0DDE.4000004@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--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.