From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=43960 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OdnKU-0008FK-NS
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:48:35 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OdnKT-0007On-AG
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:48:34 -0400
Received: from mx1.redhat.com ([209.132.183.28]:51522)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OdnKT-0007Oi-2L
	for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:48:33 -0400
Message-ID: <4C4F0DDE.4000004@redhat.com>
Date: Tue, 27 Jul 2010 19:48:30 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27
References: <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>
	<20100727164258.GS12387@redhat.com> <4C4F0D9F.1030903@redhat.com>
In-Reply-To: <4C4F0D9F.1030903@redhat.com>
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: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, Kevin Wolf <kwolf@redhat.com>, kvm@vger.kernel.org, qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>

  On 07/27/2010 07:47 PM, Avi Kivity wrote:
>  On 07/27/2010 07:42 PM, Daniel P. Berrange wrote:
>>
>>> 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).
>> We already propagate the stderr back to the client when guest startup
>> fails.
>
> I'm talking about when it doesn't fail, just spews out some warnings.
>

Note, it needn't be during startup.  If qemu says something while the 
guest is running, we need to get it to bugzilla, just like a kernel 
WARN_ON() or BUG_ON() will make it to kerneloops.org.

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