From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KdSpq-0006XO-Ld for qemu-devel@nongnu.org; Wed, 10 Sep 2008 12:46:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KdSpp-0006WH-0M for qemu-devel@nongnu.org; Wed, 10 Sep 2008 12:46:30 -0400 Received: from [199.232.76.173] (port=60822 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KdSpo-0006WA-RW for qemu-devel@nongnu.org; Wed, 10 Sep 2008 12:46:28 -0400 Received: from mail-gx0-f19.google.com ([209.85.217.19]:46549) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KdSpm-0002AP-Hf for qemu-devel@nongnu.org; Wed, 10 Sep 2008 12:46:27 -0400 Received: by mail-gx0-f19.google.com with SMTP id 12so13950055gxk.10 for ; Wed, 10 Sep 2008 09:46:26 -0700 (PDT) Message-ID: Date: Wed, 10 Sep 2008 19:46:25 +0300 From: "Blue Swirl" Subject: Re: [Qemu-devel] [PATCH 10/10] TCP based live migration In-Reply-To: <1220989802-13706-11-git-send-email-aliguori@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1220989802-13706-1-git-send-email-aliguori@us.ibm.com> <1220989802-13706-11-git-send-email-aliguori@us.ibm.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Chris Wright , Uri Lublin , Anthony Liguori , kvm@vger.kernel.org On 9/9/08, Anthony Liguori wrote: > This patch introduces a tcp protocol for live migration. It can be used as > follows: > > qemu-system-x86_64 -hda ~/images/linux-test.img -monitor stdio > > (qemu) migrate tcp:localhost:1025 > > On the same system: > > qemu-system-x86_64 -hda ~/images/linux-test.img -incoming tcp:localhost:1025 > > The monitor can be interacted with while waiting for an incoming live migration. With command line switches, you have to know when starting the VM that it is going to accept an incoming migration. Would it be possible to change this so that the incoming migration could be triggered from monitor? For example to migrate back to original host?