From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33599 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PmTdF-0002YS-0h for qemu-devel@nongnu.org; Mon, 07 Feb 2011 11:08:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PmTdD-0006IS-JW for qemu-devel@nongnu.org; Mon, 07 Feb 2011 11:08:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:57768) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PmTdD-0006I7-BT for qemu-devel@nongnu.org; Mon, 07 Feb 2011 11:08:03 -0500 Date: Mon, 7 Feb 2011 18:07:51 +0200 From: "Michael S. Tsirkin" Message-ID: <20110207160751.GC25106@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] new->old version migration List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Amit Shah Cc: Alex Williamson , qemu list , Juan Quintela New thread stated intentionally, the original patch is Message-ID: <349e93a4cfc6e1effc1b681cae53f805fdb9624e.1296713825.git.amit.shah@redhat.com> On Thu, Feb 03, 2011 at 11:47:08AM +0530, Amit Shah wrote: > Add a compat property for older machine types. When this is used (via > -M pc-0.13, for example), the new flow control mechanisms will not be > used. This is done to keep migration from a machine started with older > type on a pc-0.14+ qemu to an older machine working. > > The property is named 'flow_control' and defaults to on. > > Reported-by: Alex Williamson > Signed-off-by: Amit Shah So, I think there are two things that need to be agreed on: - Can we commit to support migration from new qemu version to an old one? We haven't in the past but downstreams do want this, so it makes sense to have the infrastructure upstream. - The infrastructure/command line option for such support. We have the -M flags to describe the machine that we are running, but that abstracts away guest-visible machine, which the migration format is not. Also, same qemu could migrate to any older version. So I think we would have to add a flag (call it -V for now) to savevm/migrate commands to specify the format to be used. Naturally some machines would be incompatible with specific -V values, that's nothing new. Pls comment. -- MST