From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPQsp-000844-EA for qemu-devel@nongnu.org; Fri, 10 Jul 2009 20:56:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPQsk-0007zq-VN for qemu-devel@nongnu.org; Fri, 10 Jul 2009 20:56:07 -0400 Received: from [199.232.76.173] (port=54097 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPQsk-0007zm-Pl for qemu-devel@nongnu.org; Fri, 10 Jul 2009 20:56:02 -0400 Received: from mail-px0-f201.google.com ([209.85.216.201]:38586) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MPQsk-0004gD-CS for qemu-devel@nongnu.org; Fri, 10 Jul 2009 20:56:02 -0400 Received: by pxi39 with SMTP id 39so767871pxi.4 for ; Fri, 10 Jul 2009 17:56:01 -0700 (PDT) Message-ID: <4A57E31D.8040001@codemonkey.ws> Date: Fri, 10 Jul 2009 19:55:57 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/3] move vm stop/start to migrate_set_state References: <1247140059-5034-1-git-send-email-pbonzini@redhat.com> <1247140059-5034-3-git-send-email-pbonzini@redhat.com> <4A55F46F.6060705@codemonkey.ws> <4A55F510.5090801@redhat.com> <4A55F641.6000701@codemonkey.ws> <20090710231424.GD30322@shareable.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: malc Cc: Paolo Bonzini , qemu-devel@nongnu.org malc wrote: > On Sat, 11 Jul 2009, Jamie Lokier wrote: > > Sounds like http://en.wikipedia.org/wiki/Two_Generals%27_Problem > And this is why the source remains in the stopped state instead of exiting after a successful migration. The only "safe" solution is to use a reliable third party which is usually going to be a management tool. If there is an undetected failure, the management tool always has the option of resuming the source node. Regards, Anthony Liguori