From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:48981) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCYnp-0003gx-JX for qemu-devel@nongnu.org; Tue, 27 Mar 2012 11:59:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SCYnh-00087J-6Q for qemu-devel@nongnu.org; Tue, 27 Mar 2012 11:59:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35656) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SCYng-00086t-Ug for qemu-devel@nongnu.org; Tue, 27 Mar 2012 11:59:13 -0400 Message-ID: <4F71E3CC.9070103@redhat.com> Date: Tue, 27 Mar 2012 17:59:08 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20120327085521.GA4567@dhcp-192-168-178-175.profitbricks.localdomain> <4F718E8B.5090601@siemens.com> In-Reply-To: <4F718E8B.5090601@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] live migration between qemu-kvm 1.0 and 0.15 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Vasilis Liaskovitis , qemu-devel@nongnu.org, kvm@vger.kernel.org On 03/27/2012 11:55 AM, Jan Kiszka wrote: > On 2012-03-27 10:55, Vasilis Liaskovitis wrote: > > Hi, > > > > is live migration between qemu-kvm stable-0.15 and stable-1.0 trees possible? > > When I live migrate a VM from 1.0 to 0.15, the destination side 0.15 qemu-kvm > > exits with: > > (qemu) Unknown savevm section or instance 'i8259' 0 > > > > That's expected, since commit "i8259:convert to qdev" 747c70af78f7088f182c87e683bdf847beead1e4 > > introduces the i8259 device in the qdev tree. > > > > The other direction (live migrate from 0.15.1 to 1.0.0) seems to work fine. > > Are any other issues expected in this direction? > > > > The vmstate for i8259 has not changed between these trees afaict. If the > > qdev-ified i8259 is reverted from stable-1.0 tree (to restore live-migration > > compatibility between the versions), would you expect problems? > > The legacy instance IDs used in old versions are not written out by > newer ones. They are just accepted on reading to allow moving forward. > There are more devices in the tree that used those instance IDs, not > only the i8259. Reverting the qdev conversion may reactivate backward > migratability for 1.0->0.15 (unless there are others as well). But that > will definitely be over after 1.1 as inrevertible code depends on the > qdev conversion. Is this true even for -M pc-0.15? -- error compiling committee.c: too many arguments to function