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 16:01:40 +0200 Message-ID: <4E944C44.1000702@redhat.com> 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> 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]:35144 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750699Ab1JKOBp (ORCPT ); Tue, 11 Oct 2011 10:01:45 -0400 In-Reply-To: <4E944B35.9070206@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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. -- error compiling committee.c: too many arguments to function