From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=48555 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OtFzF-0004So-Eu
	for qemu-devel@nongnu.org; Wed, 08 Sep 2010 04:26:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <kwolf@redhat.com>) id 1OtFzE-0001Uz-9T
	for qemu-devel@nongnu.org; Wed, 08 Sep 2010 04:26:33 -0400
Received: from mx1.redhat.com ([209.132.183.28]:6429)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <kwolf@redhat.com>) id 1OtFzE-0001Uq-0o
	for qemu-devel@nongnu.org; Wed, 08 Sep 2010 04:26:32 -0400
Message-ID: <4C8748C0.3060104@redhat.com>
Date: Wed, 08 Sep 2010 10:26:40 +0200
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] QEMU interfaces for image streaming and post-copy
	block migration
References: <4C864118.7070206@linux.vnet.ibm.com>	<AANLkTi=utpPmJwNdEYR3W8w1_BtdCYar1i8qLiubhpaf@mail.gmail.com>	<4C865160.5030600@linux.vnet.ibm.com>	<AANLkTimL5o9mPqHUXmW0Apdwu+=0-RPO-BE87WfiHYs-@mail.gmail.com>	<4C86539C.6020302@linux.vnet.ibm.com>
	<AANLkTimiSEdCERdhQ_F-7R5AQK7A9MyAUmf9eqiR+uye@mail.gmail.com>
In-Reply-To: <AANLkTimiSEdCERdhQ_F-7R5AQK7A9MyAUmf9eqiR+uye@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>, Anthony Liguori <aliguori@linux.vnet.ibm.com>, qemu-devel <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>

Am 07.09.2010 17:09, schrieb Stefan Hajnoczi:
> Right, I'm a little hesitant to get too far into discussing the
> management interface because I remember long threads about polling and
> async.  I never fully read them but I bet some wisdom came out of them
> that applies here.
> 
> There are two ways to do a long running (async?) task:
> 1. Multiple smaller pokes.  Perhaps completion of a single poke is
> async.  But the key is that the interface is incremental and driven by
> the management stack.
> 2. State.  Turn on streaming and watch it go.  You can find out its
> current state using another command which will tell you whether it is
> enabled/disabled and progress.  Use a command to disable it.

I think we need option 2 in any case for users not using libvirt. I for
one wouldn't really love to type in monitor commands every few seconds
to get the streaming done. ;-)

Let's start with this. We can always add option 1 for more sophisticated
cases later if it's desired by users.

Kevin