<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Abhishek, </div><div><br></div><div><br></div><div>These article may be useful .</div><div> - (<a href="http://blog.zhaw.ch/icclab/setting-up-live-migration-in-openstack-icehouse/">http://blog.zhaw.ch/icclab/setting-up-live-migration-in-openstack-icehouse/</a>)</div> - (<a href="http://docs.openstack.org/admin-guide-cloud/content/section_configuring-compute-migrations.html">http://docs.openstack.org/admin-guide-cloud/content/section_configuring-compute-migrations.html</a>)<div><br></div><div>If you want to easily try to live-migration , I recommended you change migration-uri from ssh to tcp.</div><div>So you may need to change the following configuration.</div><div><br></div><div>- live_migration_uri ( in nova.conf ) from "<a href="qemu+ssh://hogehoge@%s/system”">qemu+ssh://hogehoge@%s/system”</a> to “<a href="qemu+tcp://%s/system”">qemu+tcp://%s/system”</a></div><div>- listen_tls (in /etc/libvirt/libvirtd.conf ) from “1” to “0”</div><div>- listen_tcp ( in /etc/libvirt/libvritd.conf ) from “comment out” to “1”</div><div>- tcp_port ( in /etc/libvirt/libvritd.conf ) from “comment out” to “16509”</div><div>- auth_tcp ( in /etc/libvirt/libvritd.conf ) from “sasl” to “none”</div><div>- libvirtd_opts ( in /etc/default/libvirt-bin ) from “-d” to “-d -l”</div><div><br></div><div><br></div><div>I hope this information help you.</div><div><br></div><div>Yuki Nishiwaki</div><div><br><div><div>2015/06/15 21:04、Abhishek Talwar <<a href="mailto:abhishek.talwar@tcs.com">abhishek.talwar@tcs.com</a>> のメール：</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi,<br><br><p style="margin-bottom: 0cm; line-height: 10px;">I have done a multinode kilo installation with a controller, a network node and two compute nodes.</p><p style="margin-bottom: 0cm; line-height: 10px;">I am able to boot instances on both the compute nodes and they are going in to ACTIVE state.</p><p style="margin-bottom: 0cm; line-height: 10px;">When I am trying to migrate instance from one compute host to the other I am facing an error :</p><p style="margin-bottom: 0cm; line-height: 10px;"><font face="Default Sans Serif, Verdana, Arial, Helvetica, sans-serif"><font size="2" style="font-size: 10pt;"><b>[instance: 6cf0c4e2-fc9d-4db5-aeea-314271ea119f] Setting instance back to ACTIVE after: Instance rollback performed due to: Resize error: not able to execute ssh command: Unexpected error while running command.<span class="Apple-converted-space"> </span><br>Command: ssh 10.0.0.32 mkdir -p /var/lib/nova/instances/6cf0c4e2-fc9d-4db5-aeea-314271ea119f<span class="Apple-converted-space"> </span><br>Exit code: 255<span class="Apple-converted-space"> </span><br>Stdout: u''<span class="Apple-converted-space"> </span><br>Stderr: u'ssh: connect to host 10.0.0.32 port 22: Connection refused\r\n'</b></font></font></p><p style="margin-bottom: 0cm; line-height: 10px;">So how can we configure migrations in a multinode setup ? Why am I getting an SSH error ?<br></p><br>Please provide me some information regarding this.<p style="margin-bottom: 0cm; line-height: 10px;">I configured passwordless authentication between the nodes thinking it is an SSH probelm but the error remains.</p><p style="margin-bottom: 0cm; line-height: 10px;"><br></p><p style="margin-bottom: 0cm; line-height: 10px;">Regards</p><p style="margin-bottom: 0cm; line-height: 10px;">Abhishek Talwar</p><br><div></div></font><p style="margin-bottom: 0.25cm; line-height: 14px;">=====-----=====-----=====<br>Notice: The information contained in this e-mail<br>message and/or attachments to it may contain<span class="Apple-converted-space"> </span><br>confidential or privileged information. If you are<span class="Apple-converted-space"> </span><br>not the intended recipient, any dissemination, use,<span class="Apple-converted-space"> </span><br>review, distribution, printing or copying of the<span class="Apple-converted-space"> </span><br>information contained in this e-mail message<span class="Apple-converted-space"> </span><br>and/or attachments to it are strictly prohibited. If<span class="Apple-converted-space"> </span><br>you have received this communication in error,<span class="Apple-converted-space"> </span><br>please notify us by reply e-mail or telephone and<span class="Apple-converted-space"> </span><br>immediately and permanently delete the message<span class="Apple-converted-space"> </span><br>and any attachments. Thank you</p><div style="margin-bottom: 0.25cm; line-height: 14px;"><br class="webkit-block-placeholder"></div>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div></blockquote></div><br></div></body></html>