From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=40243 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P3Eax-0000oV-17 for qemu-devel@nongnu.org; Tue, 05 Oct 2010 16:58:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P3Eav-00028e-T1 for qemu-devel@nongnu.org; Tue, 05 Oct 2010 16:58:42 -0400 Received: from mx1.redhat.com ([209.132.183.28]:28673) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P3Eav-000284-MF for qemu-devel@nongnu.org; Tue, 05 Oct 2010 16:58:41 -0400 From: Alex Williamson In-Reply-To: <4CAB8F48.1050702@codemonkey.ws> References: <20101005202556.12739.14080.stgit@s20.home> <4CAB8D81.50109@codemonkey.ws> <1286311569.3136.39.camel@x201> <4CAB8F48.1050702@codemonkey.ws> Content-Type: text/plain; charset="UTF-8" Date: Tue, 05 Oct 2010 14:58:37 -0600 Message-ID: <1286312317.3136.45.camel@x201> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [RFC PATCH 0/5] Save state error handling (kill off no_migrate) List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: cam@cs.ualberta.ca, qemu-devel@nongnu.org, quintela@redhat.com On Tue, 2010-10-05 at 15:49 -0500, Anthony Liguori wrote: > On 10/05/2010 03:46 PM, Alex Williamson wrote: > > On Tue, 2010-10-05 at 15:41 -0500, Anthony Liguori wrote: > > > >> On 10/05/2010 03:35 PM, Alex Williamson wrote: > >> > >>> I was thinking of making KVM VMs with assigned PCI devices > >>> unsavable/unmigratable, but I wasn't thrilled with the > >>> no_migrate solutions. The more generic solutions seems to be > >>> simply letting save handlers return an error if the device can't > >>> be migrated. This is also much more generic than a one-way > >>> bit flip of the no_migrate flag. For a vmsd based registration, > >>> the pre_save() routine seems to be the right place to allow > >>> devices to abort. The series also carries the error back through > >>> all the vmstate callers. If this looks good, I'll give it some > >>> more testing and submit as non-RFC. Thanks, > >>> > >>> > >> Doesn't this mean that we don't fail the migration until after > >> transferring all of the memory contents? > >> > > That's the case with the current no_migrate implementation too, it > > doesn't get called until qemu_savevm_state_complete(). Thanks, > > > > Ouch, that's unfortunate but also should be easily fixable. > > But making a save handler fail seems would make it impossible to get > instant failure semantics. True. Ok, so maybe we do still need a separate no migrate registration. In any case, I think it's a good idea to allow the save routines to have a failure path, but I'll work on a way to disable migration that's not quite so coupled with the savevm entry (it seems silly for device assignment to register a savevm only for the purpose of then registering as non-migratable). Thanks, Alex