From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37348) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Whlxd-0008SD-6m for qemu-devel@nongnu.org; Tue, 06 May 2014 16:27:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WhlxX-00088Z-1D for qemu-devel@nongnu.org; Tue, 06 May 2014 16:27:33 -0400 Received: from mx1.redhat.com ([209.132.183.28]:20701) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WhlxW-00088R-Q1 for qemu-devel@nongnu.org; Tue, 06 May 2014 16:27:26 -0400 Date: Tue, 6 May 2014 23:26:12 +0300 From: "Michael S. Tsirkin" Message-ID: <20140506202612.GA15229@redhat.com> References: <1398271069-22057-1-git-send-email-dgilbert@redhat.com> <5357EF56.4010703@redhat.com> <20140423171622.GG2516@work-vm> <87sip3dvsj.fsf@blackfin.pond.sub.org> <20140424082059.GB2459@work-vm> <20140424082923.GA31845@redhat.com> <87wqeduc0d.fsf@blackfin.pond.sub.org> <20140506185807.GB8277@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140506185807.GB8277@work-vm> Subject: Re: [Qemu-devel] [RFC PATCH v2 00/16] visitor+BER migration format List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" Cc: agraf@suse.de, stefanb@linux.vnet.ibm.com, Markus Armbruster , quintela@redhat.com, qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com, aliguori@amazon.com, afaerber@suse.de On Tue, May 06, 2014 at 07:58:07PM +0100, Dr. David Alan Gilbert wrote: > * Markus Armbruster (armbru@redhat.com) wrote: > > "Michael S. Tsirkin" writes: > > > > > > OK but for a new machine type, let's default to BER, right? > > > I see no reason to keep supporting when non-BER when -M specifies 2.1 > > > compatibility, do you? > > > > I fail to see the relation between machine type and migration's wire > > encoding. > > New machine types are a useful but not definitive line in the sand. If > you enable something/change the default on a new machine type you know > it won't break any existing users since there aren't any. > > Dve Exactly. And on the other hand, someone enabling old machine type and doing live migration is likely to want to be compatible with old qemu wrt migration. > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK