[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: KVM call agenda for July 27

From: Daniel P. Berrange
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 18:01:42 +0100
User-agent: Mutt/1.4.1i

On Tue, Jul 27, 2010 at 07:42:34PM +0300, Avi Kivity wrote:
>  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

One issue though - a kernel oopps is a clear bug. A failure to start
QEMU is often just a mis-configuration, not a bug. We don't want to spa
developers with ABRT reports everytime a user misconfigures a guest.

|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

reply via email to

[Prev in Thread] Current Thread [Next in Thread]