From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Guthro Subject: Re: Re: Live Migration problems using xenapi with xm Date: Thu, 08 Nov 2007 15:18:18 -0500 Message-ID: <47336F0A.4070204@virtualiron.com> References: <4731DF7D.8000709@virtualiron.com> <47331DE2.4040400@virtualiron.com> <18227.14259.980097.937250@mariner.uk.xensource.com> <47333AF7.3070404@virtualiron.com> <47334F3C.7000607@novell.com> <18227.20703.408652.301529@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1083274410==" Return-path: In-Reply-To: <18227.20703.408652.301529@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: Jim Fehlig , xen-devel List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============1083274410== Content-Type: multipart/alternative; boundary="------------040405000207070805070404" This is a multi-part message in MIME format. --------------040405000207070805070404 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I think I have hacked together something that seems to work... HVM Live migration seems to succeed if I do the following: a.) Ignore the fact that receive thinks it is a PV guest (force is_hvm to return True) b.) Modify XendDomainInfo.waitForDevices to ignore "vkbd" and "vfb" devices for HVM guests We don't really do much PV guest stuff here, so I'm not real sure what the vfb, and vkbd are in the PV world... However, I'm not sure that they are necessary in HVM (though please correct me if I'm wrong) I'd like to come up with a patch for this, but would like to hear thoughts on what the right way to go about this is. Should I ignore those devices in waitForDevices? Should they not be there in the first place? Ian Jackson wrote: > Jim Fehlig writes ("Re: [Xen-devel] Re: Live Migration problems using xenapi with xm"): > >> I would suspect you are in uncharted territory. Currently I don't think >> there are a lot of xenapi users. In the past I have generally had to >> fix bugs or provide implementation for xenapi features previously not >> consumed by my app. You are perhaps the first to attempt migration >> (almost certainly of HVM guests) through xenapi. >> > > Jim may well be right, I'm afraid. I've only just arrived so to speak > but I think the implementation in xend certainly needs work. > > Thanks, > Ian. > --------------040405000207070805070404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I think I have hacked together something that seems to work...

HVM Live migration seems to succeed if I do the following:
a.) Ignore the fact that receive thinks it is a PV guest (force is_hvm to return True)
b.) Modify XendDomainInfo.waitForDevices to ignore "vkbd" and "vfb" devices for HVM guests

We don't really do much PV guest stuff here, so I'm not real sure what the vfb, and vkbd are in the PV world...
However, I'm not sure that they are necessary in HVM (though please correct me if I'm wrong)

I'd like to come up with a patch for this, but would like to hear thoughts on what the right way to go about this is.
Should I ignore those devices in waitForDevices?
Should they not be there in the first place?


Ian Jackson wrote: 
Jim Fehlig writes ("Re: [Xen-devel] Re: Live Migration problems using xenapi with xm"):
  
I would suspect you are in uncharted territory.  Currently I don't think
there are a lot of xenapi users.  In the past I have generally had to
fix bugs or provide implementation for xenapi features previously not
consumed by my app.  You are perhaps the first to attempt migration
(almost certainly of HVM guests) through xenapi.
    

Jim may well be right, I'm afraid.  I've only just arrived so to speak
but I think the implementation in xend certainly needs work.

Thanks,
Ian.

--------------040405000207070805070404-- --===============1083274410== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1083274410==--