From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=58065 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Odn8c-0008Q5-MX
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:36:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <chrisw@redhat.com>) id 1Odn8a-0005vA-HZ
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:36:18 -0400
Received: from mx1.redhat.com ([209.132.183.28]:20646)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <chrisw@redhat.com>) id 1Odn8a-0005uw-Al
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:36:16 -0400
Date: Tue, 27 Jul 2010 09:36:11 -0700
From: Chris Wright <chrisw@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Message-ID: <20100727163611.GD7474@x200.localdomain>
References: <4C4E1A33.7050709@codemonkey.ws>
	<m3wrshqtnc.fsf@blackfin.pond.sub.org>
	<4C4ED85B.2090807@codemonkey.ws> <4C4EDEF1.9060507@redhat.com>
	<m3d3u9kkzh.fsf@blackfin.pond.sub.org>
	<4C4EFB04.30901@codemonkey.ws> <4C4F0682.3020400@redhat.com>
	<20100727162449.GR12387@redhat.com>
	<20100727162913.GC7474@x200.localdomain>
	<4C4F0A11.5060204@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C4F0A11.5060204@redhat.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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

* 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