From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Error checking on migration? Date: Mon, 05 Jun 2006 21:50:06 -0500 Message-ID: <4484ED5E.6070503@us.ibm.com> References: <4484DFF7.5050601@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4484DFF7.5050601@hp.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Byrne Cc: xen-devel List-Id: xen-devel@lists.xenproject.org John Byrne wrote: > > I've noticed that migration doesn't fail if the VM cannot access the > disk image on the new host. (xen-unstable 10273) The VM ends up on > the new host and hangs when it does a disk access. This is a somewhat > evil behavior. You could add some basic sanity checking in XendRestore.py:restore() before xd.restore_() is invoked. A consequence of doing device setup through scripts is that the only proper way to know if a device creation will succeed is by actually creating it. It's further complicated by the race condition that results by doing the checking before actually grabbing the devices (what if another migration is in progress that happens to use the same devices). At any rate, having some sort of error checking is probably better than having none at all. Regards, Anthony Liguori > > Does anyone have a fix for this in-hand, somewhere? If not, any advice > where to look to fix the problem? > > Thanks, > > John Byrne > > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel