From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46644) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCPSG-0006eg-4z for qemu-devel@nongnu.org; Wed, 30 Jul 2014 04:41:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XCPSF-0004IO-Am for qemu-devel@nongnu.org; Wed, 30 Jul 2014 04:41:48 -0400 Received: from mail.avalus.com ([2001:41c8:10:1dd::10]:41097) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCPSF-0004IG-4V for qemu-devel@nongnu.org; Wed, 30 Jul 2014 04:41:47 -0400 Message-ID: <53D8AFBE.2060901@alex.org.uk> Date: Wed, 30 Jul 2014 09:41:34 +0100 From: Alex Bligh MIME-Version: 1.0 References: <7ad47377014a7035f4abaf6d989d34bc6885bbfd.1406703720.git.jan.kiszka@siemens.com> In-Reply-To: <7ad47377014a7035f4abaf6d989d34bc6885bbfd.1406703720.git.jan.kiszka@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/3] pc: Create 2.2 machine type List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka , "Michael S. Tsirkin" Cc: Paolo Bonzini , qemu-devel On 30/07/2014 08:02, Jan Kiszka wrote: > Yet identical to 2.1. If it's *really* identical to 2.1, are we going to add the 2.2 machine type to 2.1 as well, so that things that have difficulty using different source and destination machine types can migrate from 2.2 to 2.1? Or am I missing the point and is the issue that 2.2 is actually different to 2.1, not in the machine type definition, but in what is sent within the migrated data? If so, a commit message to this effect might be helpful. -- Alex Bligh