From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M9DHS-0001YV-Fc
	for qemu-devel@nongnu.org; Wed, 27 May 2009 03:10:30 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M9DHN-0001Gp-P6
	for qemu-devel@nongnu.org; Wed, 27 May 2009 03:10:29 -0400
Received: from [199.232.76.173] (port=48837 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M9DHN-0001GQ-Ft
	for qemu-devel@nongnu.org; Wed, 27 May 2009 03:10:25 -0400
Received: from mx20.gnu.org ([199.232.41.8]:25175)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <clalance@redhat.com>) id 1M9DHN-0007gF-4h
	for qemu-devel@nongnu.org; Wed, 27 May 2009 03:10:25 -0400
Received: from mx2.redhat.com ([66.187.237.31])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <clalance@redhat.com>) id 1M9DHL-0004dL-Fn
	for qemu-devel@nongnu.org; Wed, 27 May 2009 03:10:23 -0400
Message-ID: <4A1CE759.70109@redhat.com>
Date: Wed, 27 May 2009 09:10:17 +0200
From: Chris Lalancette <clalance@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH]: Allow monitor interaction when using migrate
	-exec
References: <4A1AAD5F.2070403@redhat.com>
In-Reply-To: <4A1AAD5F.2070403@redhat.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.gnu.org/pipermail/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: anthony@codemonkey.ws
Cc: qemu-devel@nongnu.org

Chris Lalancette wrote:
> All,
>      I've recently been playing around with migration via exec.  Unfortunately,
> when starting the incoming qemu process with "-incoming exec:cmd", it suffers
> the same problem that -incoming tcp used to suffer; namely, that you can't
> interact with the monitor until after the migration has happened.  This causes
> problems for libvirt usage of -incoming exec, since libvirt expects to be able
> to access the monitor ahead of time.  This fairly simple patch allows you to
> access the monitor both before and after the migration has completed using exec.
> 
> (note: developed/tested with qemu-kvm, but applies perfectly fine to qemu)
> 
> Signed-off-by: Chris Lalancette <clalance@redhat.com>
> 

ping?

-- 
Chris Lalancette