From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51199) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bFc2P-00027g-Kw for qemu-devel@nongnu.org; Wed, 22 Jun 2016 02:53:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bFc2L-0006Jg-89 for qemu-devel@nongnu.org; Wed, 22 Jun 2016 02:53:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42325) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bFc2L-0006Ja-2f for qemu-devel@nongnu.org; Wed, 22 Jun 2016 02:53:21 -0400 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9FE6C8535A for ; Wed, 22 Jun 2016 06:53:20 +0000 (UTC) Message-ID: <1466578399.16954.22.camel@redhat.com> From: Gerd Hoffmann Date: Wed, 22 Jun 2016 08:53:19 +0200 In-Reply-To: <1466536447-30146-1-git-send-email-dgilbert@redhat.com> References: <1466536447-30146-1-git-send-email-dgilbert@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 00/13] virtio migration: Flip outer layer to vmstate List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert (git)" Cc: qemu-devel@nongnu.org, mst@redhat.com, amit.shah@redhat.com, quintela@redhat.com Hi, > I think the first two patches are the most controversial; > they remove migration support for old version of virtio-net and virtio-se= rial; > (for virtio-net versions prior to 0.11 and for virtio-serial prior to 0.1= 3). > I'm working on the basis that migration has bit rotted enough so > that the streams aren't migration compatible for that long back > on upstream - but if anyone knows otherwise please shout. We've gone great lengths to avoid new versions by using subsections instead for *years*. So if we are going to cut live migration support from ancient versions now: Can we possibly remove the versioning altogether? cheers, Gerd