<div dir="ltr">finally, i found the problem, qemu-img create command not specific vm disk size on target host, when i use the size same as source vm, the migration finish successfully.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 23, 2018 at 7:56 PM, Michal Privoznik <span dir="ltr"><<a href="mailto:mprivozn@redhat.com" target="_blank">mprivozn@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/23/2018 01:26 PM, cokabug wrote:<br>
> Hi ,<br>
> <br>
> when i have run virsh migrate command , the migration progress fiailed<br>
> at [61 %].<br>
> command :<br>
> virsh migrate --live --undefinesource --p2p --copy-storage-inc<br>
> --verbose --persistent instance-00001959 qemu+tcp://host292/system<br>
> <br>
> result :<br>
> Migration: [ 61 %]error: operation failed: migration job: unexpectedly<br>
> failed<br>
> <br>
> os/kernel version: centos 6.7 / kernel 2.6.32<br>
> qemu-kvm version : 0.12.1.2<br>
> libvirt version : 0.10.2-54<br>
<br>
</span>These are very ancient versions. I wouldn't be surprised if you upgrade<br>
and find out the problem is fixed.<br>
<span class=""><br>
> <br>
> the libvirt.log on target host:<br>
> 2018-05-22 11:45:38.603+0000: 32314: warning : qemuDomainObjTaint:1459<br>
> : Domain id=30 name='instance-00001959'<br>
> uuid=41975d30-2490-473e-be7b-<wbr>9d2d08bf66d2 is tainted: high-privileges<br>
> 2018-05-22 11:45:38.883+0000: 32314: warning :<br>
> qemuDomainObjEnterMonitorInter<wbr>nal:1062 : This thread seems to be the async<br>
> job owner; entering monitor without asking for a nested job is dangerous<br>
> 2018-05-22 11:45:38.902+0000: 32314: warning :<br>
> qemuDomainObjEnterMonitorInter<wbr>nal:1062 : This thread seems to be the async<br>
> job owner; entering monitor without asking for a nested job is dangerous<br>
> 2018-05-22 11:45:38.903+0000: 32314: warning :<br>
> qemuDomainObjEnterMonitorInter<wbr>nal:1062 : This thread seems to be the async<br>
> job owner; entering monitor without asking for a nested job is dangerous<br>
> 2018-05-22 11:45:39.090+0000: 32314: warning :<br>
> qemuDomainObjEnterMonitorInter<wbr>nal:1062 : This thread seems to be the async<br>
> job owner; entering monitor without asking for a nested job is dangerous<br>
> 2018-05-22 11:45:39.090+0000: 32314: warning :<br>
> qemuDomainObjEnterMonitorInter<wbr>nal:1062 : This thread seems to be the async<br>
> job owner; entering monitor without asking for a nested job is dangerous<br>
> 2018-05-22 11:45:39.091+0000: 32314: warning :<br>
> qemuDomainObjEnterMonitorInter<wbr>nal:1062 : This thread seems to be the async<br>
> job owner; entering monitor without asking for a nested job is dangerous<br>
> 2018-05-22 11:45:41.841+0000: 32310: error : qemuMonitorIO:615 : internal<br>
> error End of file from monitor<br>
> <br>
<br>
</span>This says that qemu died. You can try to look into domain log to see why.<br>
<span class="HOEnZb"><font color="#888888"><br>
Michal<br>
</font></span></blockquote></div><br></div>