Upon some close investigation it looks like crm_resource only issues a
stop on the node that is running the Xen guest and then a start on the
destination host. I can hack the Xen OCF resource script to make live
migration work but this does not look like the right way to do it. How
can I get crm_resource to actually make a migrate_to call?
- Stefano
Stefano Harding wrote:
Lars,
Yes, xm migrate works fine. I have been able to successfully migrate
guests to any of the five nodes. But when I do crm_resource -M -r cvs
-H ca1xnc04 for example the guest CVS is stopped on the running node,
then started on the destination host ca1xnc04. I didn't know if my
cib.xml was missing something or if there was a particular way to do
the migrate?
- Stefano
Lars Marowsky-Bree wrote:
On 2007-06-11T12:06:46, Stefano Harding <[EMAIL PROTECTED]> wrote:
Hello all!
I am trying to figure out how I can do a Xen live migration. I have a
five node cluster running Fedora 6, Xen 3.0.3 and Heartbeat 2.1.0-21.1.
The OCF file for Xen has the option Xen_Migrate_To and Xen_Migrate_From
but how do I access this with crm_resource? Doing a crm_resource -M -r
my_resource -H destination_host stops/starts the guest host or is there
some other way to do a live migration? My cib.xml file is listed below.
I did add the meta_attributes allow_migrate but that still has no effect.
That's all what is needed from heartbeat/CRM.
Assuming that your Xen cluster itself is configured to allow live
migration. Does xm migrate work for a non-heartbeat managed DomU when
you invoke it on the commandline?
Regards,
Lars
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
