<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>Thanks for looking into the details Ruben. I figured out later that the migration was failing because of last migration reason being 'none'. I resolved this issue by deleting last migration records from 'history' and 'vm_pool' tables. I will try out the
patch soon.</div>
<div><br>
</div>
<div>--</div>
<div>Shantanu</div>
<br>
<div>
<div>On Aug 2, 2012, at 6:37 PM, Ruben S. Montero wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">Hi,
<div><br>
</div>
<div>It seems that after a migration fail, that last history record was not updated in the DB. If OpenNebula is restarted (or the VM flushed from memory) that record will be restored with the last available REASON, that was none. This, as reported, prevents
the VM from being migrated again.</div>
<div><br>
</div>
<div>You can find a patch for this at [1]</div>
<div><br>
</div>
<div>Cheers, and thanks for your feedback</div>
<div><br>
</div>
<div>Ruben</div>
<div>
<div>[1] <a href="http://dev.opennebula.org/projects/opennebula/repository/revisions/cabf3b417e62d87c9cfe465301e5cc6e6e5865b0/diff/src/lcm/LifeCycleStates.cc">http://dev.opennebula.org/projects/opennebula/repository/revisions/cabf3b417e62d87c9cfe465301e5cc6e6e5865b0/diff/src/lcm/LifeCycleStates.cc</a></div>
<div><br>
</div>
<div>Link to issue:</div>
<div><a href="http://dev.opennebula.org/issues/1400">http://dev.opennebula.org/issues/1400</a></div>
<div><br>
</div>
-- <br>
Ruben S. Montero, PhD<br>
Project co-Lead and Chief Architect<br>
OpenNebula - The Open Source Solution for Data Center Virtualization<br>
<a href="http://www.OpenNebula.org/" target="_blank">www.OpenNebula.org</a> | <a href="mailto:rsmontero@opennebula.org" target="_blank">
rsmontero@opennebula.org</a> | @OpenNebula<br>
</div>
</blockquote>
</div>
<br>
</body>
</html>