From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=57482 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Odn4n-0005SR-6n
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:32:22 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1Odn4m-0005VL-5r
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:32:21 -0400
Received: from mx1.redhat.com ([209.132.183.28]:19952)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1Odn4l-0005VH-SF
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:32:20 -0400
Message-ID: <4C4F0A11.5060204@redhat.com>
Date: Tue, 27 Jul 2010 19:32:17 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
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>
	<20100727162913.GC7474@x200.localdomain>
In-Reply-To: <20100727162913.GC7474@x200.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Chris Wright <chrisw@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>

  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.

-- 
error compiling committee.c: too many arguments to function