----- Original Message -----
From: "Shu Ming" <shuming(a)linux.vnet.ibm.com>
To: "VDSM Project Development" <vdsm-devel(a)lists.fedorahosted.org>
Sent: Wednesday, July 25, 2012 5:57:05 PM
Subject: [vdsm] Fatal error when migrate the VM with disk on iscsi data center
Hi,
I am testing the VM migration in oVirt engine 3.1 bteta release and
successfully did the migration test on NFS date center. However, the
test of VM migration on iSCSI data center failed.
I dumped the error and warning segments from the vdsm logs on both
the source and destination host. Please ignore the time stamp out of
sync between the two hosts.
The vdsm log segment from the source host:
66-4da5-8310-6dcc970e5367`::migration downtime thread exiting
Thread-115166::ERROR::2012-07-25
23:18:55,953::vm::176::vm.Vm::(_recover)
vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::operation failed:
Failed to connect to remote libvirt URI
qemu+tcp://9.181.129.110/system
Dummy-115148::DEBUG::2012-07-25
23:18:55,981::__init__::1249::Storage.Misc.excCmd::(_log) 'dd
if=/rhev/data-center/0b9a4ea4-d487-11e1-b614-5254001498c4/mastersd/dom_md/inbox
iflag=direct,fullblock count=1 bs=1024000' (cwd None)
Thread-115166::ERROR::2012-07-25 23:18:56,028::vm::240::vm.Vm::(run)
vmId=`11e06222-2d66-4da5-8310-6dcc970e5367`::Failed to migrate
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 223, in run
self._startUnderlyingMigration()
File "/usr/share/vdsm/libvirtvm.py", line 451, in
_startUnderlyingMigration
None, maxBandwidth)
File "/usr/share/vdsm/libvirtvm.py", line 491, in f
ret = attr(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
line 82, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1034, in
migrateToURI2
if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed',
dom=self)
libvirtError: operation failed: Failed to connect to remote libvirt
URI qemu+tcp://9.181.129.110/system
The destination host doesn't look right (9.181.129.110).
Can you post the logs related to the vmMigrate parameters?
Eventually you could open a bug so that you can attach the full logs.
--
Federico