From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=35130 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OdnF9-0004SL-Sz for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:43:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OdnF8-0006lk-7p for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:43:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4150) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OdnF7-0006la-VB for qemu-devel@nongnu.org; Tue, 27 Jul 2010 12:43:02 -0400 Date: Tue, 27 Jul 2010 17:42:58 +0100 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Re: KVM call agenda for July 27 Message-ID: <20100727164258.GS12387@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100727162913.GC7474@x200.localdomain> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chris Wright Cc: Kevin Wolf , kvm@vger.kernel.org, qemu-devel@nongnu.org, Markus Armbruster , Avi Kivity On Tue, Jul 27, 2010 at 09:29:13AM -0700, Chris Wright wrote: > * 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). We already propagate the stderr back to the client when guest startup fails. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|