qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	kvm@vger.kernel.org, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 09:36:11 -0700	[thread overview]
Message-ID: <20100727163611.GD7474@x200.localdomain> (raw)
In-Reply-To: <4C4F0A11.5060204@redhat.com>

* Avi Kivity (avi@redhat.com) wrote:
>  On 07/27/2010 07:29 PM, Chris Wright wrote:
> >
> >>QEMU stderr+out is already recorded in /var/lib/libvirt/qemu/$GUESTNAME.log
> >>along with the env variables and argv used to spawn it. Or did you mean
> >>provide an API + virsh command /virt-manager UI for accessing the logs ?
> >I read that to mean...propagate stderr from qemu to be right in front of
> >the user.
> 
> Yes, that's what I meant.
> 
> >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).
> 
> If things work there's  no reason for the user to go look at the
> logs.  An exclamation point invites clicking.
> 
> Even better would be an ABRT plugin, so if something goes
> (marginally) wrong, the siren pops up and you're invited to report
> the bug.

Despite some of the ABRT growing pains, ABRT plugin seems like a good
idea.  I don't know enough of the plugins to know if that requires
formatted output and just grepping for some known regexps.

thanks,
-chris

  reply	other threads:[~2010-07-27 16:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 21:28 [Qemu-devel] KVM call agenda for July 27 Chris Wright
2010-07-26 22:28 ` [Qemu-devel] " Anthony Liguori
2010-07-26 23:28   ` Anthony Liguori
2010-07-27  0:13     ` Alex Williamson
2010-07-27 13:22       ` Jes Sorensen
2010-07-27  7:19     ` Markus Armbruster
2010-07-27 13:00       ` Anthony Liguori
2010-07-27 13:28         ` Kevin Wolf
2010-07-27 15:22           ` Markus Armbruster
2010-07-27 15:28             ` Anthony Liguori
2010-07-27 15:37               ` Daniel P. Berrange
2010-07-27 16:17               ` Avi Kivity
2010-07-27 16:24                 ` Daniel P. Berrange
2010-07-27 16:29                   ` Chris Wright
2010-07-27 16:32                     ` Avi Kivity
2010-07-27 16:36                       ` Chris Wright [this message]
2010-07-27 16:42                         ` Avi Kivity
2010-07-27 17:01                           ` Daniel P. Berrange
2010-07-27 17:37                             ` Avi Kivity
2010-07-27 16:42                     ` Daniel P. Berrange
2010-07-27 16:47                       ` Avi Kivity
2010-07-27 16:48                         ` Avi Kivity
2010-07-28 11:22               ` Markus Armbruster
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 13:30     ` Anthony Liguori
2010-07-27 13:43       ` 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=20100727163611.GD7474@x200.localdomain \
    --to=chrisw@redhat.com \
    --cc=armbru@redhat.com \
    --cc=avi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).