From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM call agenda for October 11th Date: Tue, 11 Oct 2011 15:47:47 +0200 Message-ID: <4E944903.4020206@redhat.com> References: <4E942CFA.5040403@redhat.com> <4E943E21.10501@codemonkey.ws> <4E9442EC.8020903@redhat.com> <4E944440.1080109@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: qemu-devel@nongnu.org, KVM devel mailing list , quintela@redhat.com To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:15872 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751118Ab1JKNrx (ORCPT ); Tue, 11 Oct 2011 09:47:53 -0400 In-Reply-To: <4E944440.1080109@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 10/11/2011 03:27 PM, Anthony Liguori wrote: >> 5) Implement subsections through the wire as top-level sections (as >> originally intended). Keep existing subsections with (1). > > > That was (3). > Yes, sorry. >> btw, it's reasonable to require that backwards migration is only to a >> fully updated stable release, so we can do 5) too, or backport 1). > > But given the choice of a nasty silent failure to an > not-quite-up-to-date stable release or failing migration to a fully > up-to-date stable release, I think it's better that we err on the side > of caution. We're erring on the side of no migration, it seems. > Not being able to migrate because of a recoverable failure is > annoying. Having a silent failure that possible results in corruption > is unacceptable. What I'm trying to avoid is making choices today that close the door on better fixes in the future. -- error compiling committee.c: too many arguments to function