<div dir="ltr">Hi Cherish,</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 19, 2012 at 1:11 AM, bin chen <span dir="ltr"><<a href="mailto:free2coder@gmail.com" target="_blank">free2coder@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span style="line-height:23px;font-size:14px">Hi,all</span><div style="line-height:23px;font-size:14px">
My cluster is pacemaker 1.1.7 + corosync 2.0. I have write a resource agent to manage the virtual machine.The RA supports start,stop,migrate_from,migrate_to,monitor.</div>
<div style="line-height:23px;font-size:14px"> But when I try to migrate a running cluster vm(resource name is dcbh6f1c-GtNhnB-8597) from the host(h66) to a target host (h65),the cluster just stops it in host A,and then start it in host B.</div>
</div></blockquote><div><br></div><div><div dir="ltr"><div><br></div><div>Can we safely assume that you are certain you have live migration working without the cluster involved? E.g. you can do an 'xm migrate' or 'virsh migrate', whatever you're using to manage your VMs?</div>
<div><br></div><div>Have you set "allow-migrate=true" for the VM resource? This snip is showing the Xen RA, but the VirtualDomain RA has the same option, I believe:</div><div><br></div><div>---- 8< ----</div>
<div>primitive www3 ocf:heartbeat:Xen \</div><div><span style="white-space:pre-wrap"> </span>params xmfile="/etc/xen/www3" \</div><div><span style="white-space:pre-wrap"> </span>meta allow-migrate="true" target-role="Started" is-managed="true" \</div>
</div><div class="gmail_extra">---- 8< ----</div><div class="gmail_extra"><br></div><div class="gmail_extra">If you already have that set, then your cluster configuration would be good to see.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">Regards,</div><div class="gmail_extra">Mark</div></div></div></div>