From: Avi Kivity <avi@redhat.com>
To: Chris Wright <chrisw@redhat.com>
Cc: 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:42:34 +0300 [thread overview]
Message-ID: <4C4F0C7A.4030309@redhat.com> (raw)
In-Reply-To: <20100727163611.GD7474@x200.localdomain>
On 07/27/2010 07:36 PM, Chris Wright wrote:
>
>> 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.
It's annoying to us old hands, but it does give that nice integrated
system feel that we're missing, and it works even if virt-manager is in
the background (or if you don't use virt-manager at all).
Given that there's a kerneloops pluging that presumably does similar
parsing, I don't think it's too hard:
$ size /usr/lib64/abrt/libKerneloopsScanner.so
text data bss dec hex filename
18293 1416 16 19725 4d0d
/usr/lib64/abrt/libKerneloopsScanner.so
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-07-27 16:42 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
2010-07-27 16:42 ` Avi Kivity [this message]
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=4C4F0C7A.4030309@redhat.com \
--to=avi@redhat.com \
--cc=armbru@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 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).