The nodes are EL6.3 based.

Currently installed libvirt packages:

libvirt-lock-sanlock-0.9.10-21.el6_3.8.x86_64
libvirt-cim-0.6.1-3.el6.x86_64
libvirt-0.9.10-21.el6_3.8.x86_64
libvirt-python-0.9.10-21.el6_3.8.x86_64
libvirt-client-0.9.10-21.el6_3.8.x86_64

and qemu packages:
qemu-kvm-0.12.1.2-2.295.el6_3.10.x86_64
qemu-kvm-tools-0.12.1.2-2.295.el6_3.10.x86_64
qemu-img-0.12.1.2-2.295.el6_3.10.x86_64

Thus my presumption here given the above is that virDomainMigrateToURI2 has not yet been patched and/or back-ported into the EL6.x libvirt/qemu?

- DHC


On Wed, Jan 30, 2013 at 1:28 PM, Dan Kenigsberg <danken@redhat.com> wrote:
On Wed, Jan 30, 2013 at 11:04:00AM -0600, Dead Horse wrote:
> Engine Build --> Commit: 82bdc46dfdb46b000f67f0cd4e51fc39665bf13b
> VDSM Build: --> Commit: da89a27492cc7d5a84e4bb87652569ca8e0fb20e + patch
> --> http://gerrit.ovirt.org/#/c/11492/
>
> Engine Side:
> 2013-01-30 10:56:38,439 ERROR
> [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo]
> (QuartzScheduler_Worker-70) Rerun vm 887d764a-f835-4112-9eda-836a772ea5eb.
> Called from vds lostisles
> 2013-01-30 10:56:38,506 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) START, MigrateStatusVDSCommand(HostName = lostisles,
> HostId = e042b03b-dd4e-414c-be1a-b2c65ac000f5,
> vmId=887d764a-f835-4112-9eda-836a772ea5eb), log id: 6556e75b
> 2013-01-30 10:56:38,510 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) Failed in MigrateStatusVDS method
> 2013-01-30 10:56:38,510 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) Error code migrateErr and error message
> VDSGenericException: VDSErrorException: Failed to MigrateStatusVDS, error =
> Fatal error during migration
> 2013-01-30 10:56:38,511 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand]
> (pool-3-thread-49) Command
> org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand return
> value
>  StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=12,
> mMessage=Fatal error during migration]]
>
>
> VDSM Side:
> Thread-43670::ERROR::2013-01-30 10:56:37,052::vm::200::vm.Vm::(_recover)
> vmId=`887d764a-f835-4112-9eda-836a772ea5eb`::this function is not supported
> by the connection driver: virDomainMigrateToURI2
> Thread-43670::ERROR::2013-01-30 10:56:37,513::vm::288::vm.Vm::(run)
> vmId=`887d764a-f835-4112-9eda-836a772ea5eb`::Failed to migrate
> Traceback (most recent call last):
>   File "/usr/share/vdsm/vm.py", line 273, in run
>     self._startUnderlyingMigration()
>   File "/usr/share/vdsm/libvirtvm.py", line 504, in
> _startUnderlyingMigration
>     None, maxBandwidth)
>   File "/usr/share/vdsm/libvirtvm.py", line 540, in f
>     ret = attr(*args, **kwargs)
>   File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line
> 111, in wrapper
>     ret = f(*args, **kwargs)
>   File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1103, in
> migrateToURI2
>     if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed',
> dom=self)
> libvirtError: this function is not supported by the connection driver:
> virDomainMigrateToURI2

Could it be that you are using an ancient libvirt with no
virDomainMigrateToURI2? What are your libvirt and qemu-kvm versions (on
both machines)?