Hi Devdeep, This is regarding XenMotion, I have noticed few known issues specified in the given link such as :
1. When migrating VMs using Storage XenMotion, attempts to cancel the operation may not delete the temporary virtual disks. [CA-87710] [CA-87689] 2. When a VM is unexpectedly shut down during a Storage XenMotion migration, the migration may fail. This process may leave a shut down incomplete copy of the VM on the destination pool. Customers should delete the VM from the destination pool and re try the operation with the VM running. [CA-86347 So will you be handling these operations which are expected to fail from Xenserver ? Thanks and Regards, Sailaja.M -----Original Message----- From: Devdeep Singh [mailto:[email protected]] Sent: Tuesday, December 04, 2012 4:49 PM To: [email protected] Subject: Adding support for XenServer 6.1 and Storage XenMotion Hi, With XenServer 6.1, support for storage xenmotion has been added in XenServer. I am planning to work on enabling support for XenServer 6.1 and storage xenmotion in CloudStack. It'll involve the following activities: 1. Enable support in CloudStack for XenServer 6.1. There is already a bug filed for it, see [1]. 2. Update the java bindings that are used by CloudStack for making xapi calls. The current bindings are present under deps/XenServerJava in source tree. They need to be updated for getting the new apis that have been added for supporting storage xenmotion. CloudStack has made customizations to these bindings to address certain issues. They'll also be ported. 3. Enable support for storage xenmotion from CloudStack, see [2]. I'll share a FS for this in the next few days. Do let me know your thoughts/concerns. [1] https://issues.apache.org/jira/browse/CLOUDSTACK-369 [2] http://support.citrix.com/article/CTX134582#newfeatures Regards, Devdeep
