From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDdY8-0001aD-TU for qemu-devel@nongnu.org; Tue, 11 Oct 2011 10:43:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDdY1-0001Mj-VA for qemu-devel@nongnu.org; Tue, 11 Oct 2011 10:43:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59404) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDdY1-0001Mc-OB for qemu-devel@nongnu.org; Tue, 11 Oct 2011 10:43:13 -0400 Message-ID: <4E9455FC.1000607@redhat.com> Date: Tue, 11 Oct 2011 16:43:08 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4E942CFA.5040403@redhat.com> <4E943E21.10501@codemonkey.ws> <4E9442EC.8020903@redhat.com> <4E944440.1080109@codemonkey.ws> <4E944903.4020206@redhat.com> <4E944B35.9070206@codemonkey.ws> <4E944C44.1000702@redhat.com> <4E9453E1.20009@codemonkey.ws> In-Reply-To: <4E9453E1.20009@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for October 11th List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, KVM devel mailing list , quintela@redhat.com On 10/11/2011 04:34 PM, Anthony Liguori wrote: > On 10/11/2011 09:01 AM, Avi Kivity wrote: >> On 10/11/2011 03:57 PM, Anthony Liguori wrote: >>>> What I'm trying to avoid is making choices today that close the >>>> door on >>>> better fixes in the future. >>> >>> >>> I think Juan made a really good point in his earlier post. We need to >>> focus on better testing for migration. With a solid migration torture >>> test, we can probably eliminate much of the problems we're facing >>> today. >> >> Agree, fingerprinting vmstate should help a lot. Actually I don't think >> the visitor is strictly required, the fingerprinter can just walk >> vmstate structs. > > You mean generating a schema? Dumping the vmstate descriptions in a canonical format, and having a tools that verifies that version A is compatible with version B. > I was talking about an active migration torture test. Those are good, but inherently limited. -- error compiling committee.c: too many arguments to function