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:17:06 +0300 Message-ID: <4C4F0682.3020400@redhat.com> References: <20100726212849.GB2651@x200.localdomain> <4C4E0C05.5030004@codemonkey.ws> <4C4E1A33.7050709@codemonkey.ws> <4C4ED85B.2090807@codemonkey.ws> <4C4EDEF1.9060507@redhat.com> <4C4EFB04.30901@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Markus Armbruster , Kevin Wolf , Chris Wright , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:25176 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751159Ab0G0QRK (ORCPT ); Tue, 27 Jul 2010 12:17:10 -0400 In-Reply-To: <4C4EFB04.30901@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function