From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MOu3m-0004wJ-TQ
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:53:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MOu3h-0004sA-VN
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:53:14 -0400
Received: from [199.232.76.173] (port=36583 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MOu3h-0004rx-4M
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:53:09 -0400
Received: from mail-qy0-f174.google.com ([209.85.221.174]:60388)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MOu3g-0001xZ-Rr
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:53:08 -0400
Received: by qyk4 with SMTP id 4so95146qyk.4
	for <qemu-devel@nongnu.org>; Thu, 09 Jul 2009 06:53:08 -0700 (PDT)
Message-ID: <4A55F641.6000701@codemonkey.ws>
Date: Thu, 09 Jul 2009 08:53:05 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
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>
In-Reply-To: <4A55F510.5090801@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org

Paolo Bonzini wrote:
> On 07/09/2009 03:45 PM, Anthony Liguori wrote:
>> How does the disk become full during the final stage?  The guest isn't
>> running.
>
> The host disk can become full and cause a "migrate exec" to fail.  Or 
> for network migration migration, you could have the connection drop 
> exactly during the final stage.  In this case, the VM would be 
> unconditionally restarted.

Because migration failed.  Is that not the desired behavior?  It seems 
like it is to me.

If I try to do a live migration, it should either succeed and my guest 
experiences minimal downtime or it should fail and my guest should 
experience minimal downtime.

Regards,

Anthony Liguori

> Paolo