From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=35081 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Odn1p-0004SL-P1
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:29:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <chrisw@redhat.com>) id 1Odn1o-00055I-JI
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:29:17 -0400
Received: from mx1.redhat.com ([209.132.183.28]:1025)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <chrisw@redhat.com>) id 1Odn1o-00055E-As
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:29:16 -0400
Date: Tue, 27 Jul 2010 09:29:13 -0700
From: Chris Wright <chrisw@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
Message-ID: <20100727162913.GC7474@x200.localdomain>
References: <20100726212849.GB2651@x200.localdomain>
	<4C4E0C05.5030004@codemonkey.ws> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100727162449.GR12387@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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Chris Wright <chrisw@redhat.com>, kvm@vger.kernel.org, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>

* Daniel P. Berrange (berrange@redhat.com) wrote:
> On Tue, Jul 27, 2010 at 07:17:06PM +0300, Avi Kivity wrote:
> >  On 07/27/2010 06:28 PM, Anthony Liguori wrote:
> > >
> > >If we add docs/deprecated-features.txt, schedule removal for at least 
> > >1 year in the future, and put a warning in the code that prints 
> > >whenever raw is probed, I think I could warm up to this.
> > >
> > >Since libvirt should be insulating users from this today, I think the 
> > >fall out might not be terrible.
> > 
> > On a related note, we should ask libvirt to make qemu stderr output 
> > available to its users, or perhaps an ABRT plugin to report such 
> > messages from libvirt's logs.
> 
> 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.  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).

thanks,
-chris