From mboxrd@z Thu Jan 1 00:00:00 1970 From: Uri Lublin Subject: Re: [PATCH]: Make migration handle errors a little better Date: Thu, 24 Jan 2008 13:01:53 +0200 Message-ID: <47987021.6010203@qumranet.com> References: <4797997A.1050809@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Chris Lalancette Return-path: In-Reply-To: <4797997A.1050809-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Chris Lalancette wrote: > All, > Attached is a fairly simple patch to the migration code to make it handle > errors better. In particular, if the remote side wasn't set up properly (i.e. > the memory size didn't match), the migration would fail, but the source host > didn't actually react properly, so the migration would still be "in-progress". > This patch fixes up the error checking to properly quit when the remote side > isn't prepared for whatever reason. > > Signed-off-by: Chris Lalancette > Patch looks good. Why did you define MIG_STAT_DIRTY_TRACK_FAIL and not MIG_STAT_KVM_SET_DIRTY_TRACKING_FAILED ? Also we need to make sure, in case of a failure, that 'status' is updated and *s->has_error is freed. How about calling migrate_finish ? Thanks, Uri. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/