From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCbdt-0005HN-6U for qemu-devel@nongnu.org; Mon, 23 Nov 2009 11:19:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCbdo-0005G4-2j for qemu-devel@nongnu.org; Mon, 23 Nov 2009 11:19:56 -0500 Received: from [199.232.76.173] (port=45071 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCbdn-0005Fu-PE for qemu-devel@nongnu.org; Mon, 23 Nov 2009 11:19:51 -0500 Received: from mail-qy0-f194.google.com ([209.85.221.194]:52640) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NCbdn-0004lp-DB for qemu-devel@nongnu.org; Mon, 23 Nov 2009 11:19:51 -0500 Received: by qyk32 with SMTP id 32so2603063qyk.4 for ; Mon, 23 Nov 2009 08:19:51 -0800 (PST) Message-ID: <4B0AB622.1040302@codemonkey.ws> Date: Mon, 23 Nov 2009 10:19:46 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <20091123123640.GL2999@redhat.com> <20091123143242.GO2999@redhat.com> <4B0AA165.60900@codemonkey.ws> <20091123145356.GQ2999@redhat.com> <4B0AA4D6.9060607@codemonkey.ws> <20091123152252.GR2999@redhat.com> <4B0AAB20.8060109@codemonkey.ws> <20091123154951.GT2999@redhat.com> <4B0AB3AB.5080204@codemonkey.ws> <20091123161504.GY2999@redhat.com> In-Reply-To: <20091123161504.GY2999@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Live migration protocol, device features, ABIs and other beasts List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Paolo Bonzini , Juan Quintela , qemu-devel@nongnu.org Gleb Natapov wrote: > I am OK with management being responsible to sort things out. Juan > said that destination can't abort migration in the middle, so I pointed > out easy solution that will work in 99.999% cases. > I think there's something elegant about doing migration in a unidirectional stream. It makes live migration work to a file, to a qcow2 file, etc. with no protocol change. The ack'ing bits can be done by a live migration transport since it happens entirely at the end of the stream. The old ssh: migration used to do this and provided a simple means that worked 99.999% of the time :-) Regards, Anthony Liguori > -- > Gleb. >