Re: [libvirt-users] virsh migration job unexpectedly failed

On 05/23/2018 01:26 PM, cokabug wrote: > Hi , > > when i have run virsh migrate command , the migration progress fiailed > at [61 %]. > command : > virsh migrate --live --undefinesource --p2p --copy-storage-inc > --verbose --persistent instance-00001959 qemu+tcp://host292/system > > result : > Migration: [ 61 %]error: operation failed: migration job: unexpectedly > failed > > os/kernel version: centos 6.7 / kernel 2.6.32 > qemu-kvm version : 0.12.1.2 > libvirt version : 0.10.2-54 These are very ancient versions. I wouldn't be surprised if you upgrade and find out the problem is fixed. > > the libvirt.log on target host: > 2018-05-22 11:45:38.603+0000: 32314: warning : qemuDomainObjTaint:1459 > : Domain id=30 name='instance-00001959' > uuid=41975d30-2490-473e-be7b-9d2d08bf66d2 is tainted: high-privileges > 2018-05-22 11:45:38.883+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:38.902+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:38.903+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:39.090+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:39.090+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:39.091+0000: 32314: warning : > qemuDomainObjEnterMonitorInternal:1062 : This thread seems to be the async > job owner; entering monitor without asking for a nested job is dangerous > 2018-05-22 11:45:41.841+0000: 32310: error : qemuMonitorIO:615 : internal > error End of file from monitor > This says that qemu died. You can try to look into domain log to see why. Michal