<div dir="ltr">Hello!<div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 24, 2017 at 3:55 PM, Ralf Schenk <span dir="ltr"><<a href="mailto:rs@databay.de" target="_blank">rs@databay.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p><span style="font-family:Helvetica,Arial,sans-serif">nice to hear it worked
for you.</span><br></p>
<p><font face="Helvetica, Arial, sans-serif">Attached you find the
vdsm.log </font><font face="Helvetica, Arial, sans-serif"><font face="Helvetica, Arial, sans-serif">(from migration source)
including the error </font>and engine.log which looks ok.</font></p></div></blockquote><div><br></div><div>Yes, most interesting part was in the vdsm log. Do you have anything interesting in gluster logs?</div><div><br></div><div>And another one - can you try to run that vm (or some new vm with drives on the same SD) on the migration target host? Will it start?</div></div></div></div>