From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:46822) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qeimo-0005TT-Q8 for qemu-devel@nongnu.org; Thu, 07 Jul 2011 03:14:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qeimn-0004Kz-3n for qemu-devel@nongnu.org; Thu, 07 Jul 2011 03:14:10 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63968) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qeimm-0004Kt-KW for qemu-devel@nongnu.org; Thu, 07 Jul 2011 03:14:08 -0400 Message-ID: <4E155CB9.4020009@redhat.com> Date: Thu, 07 Jul 2011 09:14:01 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <4E148776.4000805@redhat.com> <4E149B3F.2010709@redhat.com> <4E14BF36.3080803@codemonkey.ws> <6E6E2CFC-B5BB-4E1D-945D-1F13C604330B@suse.de> In-Reply-To: <6E6E2CFC-B5BB-4E1D-945D-1F13C604330B@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] migration: new sections and backward compatibility. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Juan Quintela , jes sorensen , Markus Armbruster , "qemu-devel@nongnu.org" , Avi Kivity Hi, >> We don't have a hard policy about not merging devices that don't >> support migration. >> >> Since migration must be supported forever, I'd rather see a device >> get some solid testing before it starts doing live migration. That >> said, we should probably do this consciously by explicitly marking >> the device non-migrateable. > > Can't we just implicitly fail migration whenever there's a device in > the tree that doesn't have VMSTATE? There are cases where the device doesn't need to save state, so that alone doesn't cut it. cheers, Gerd