From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27 Date: Tue, 27 Jul 2010 19:47:27 +0300 Message-ID: <4C4F0D9F.1030903@redhat.com> References: <4C4E0C05.5030004@codemonkey.ws> <4C4E1A33.7050709@codemonkey.ws> <4C4ED85B.2090807@codemonkey.ws> <4C4EDEF1.9060507@redhat.com> <4C4EFB04.30901@codemonkey.ws> <4C4F0682.3020400@redhat.com> <20100727162449.GR12387@redhat.com> <20100727162913.GC7474@x200.localdomain> <20100727164258.GS12387@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chris Wright , Anthony Liguori , Markus Armbruster , Kevin Wolf , kvm@vger.kernel.org, qemu-devel@nongnu.org To: "Daniel P. Berrange" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18480 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751778Ab0G0Qrb (ORCPT ); Tue, 27 Jul 2010 12:47:31 -0400 In-Reply-To: <20100727164258.GS12387@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function