[ovirt-users] Error migrating VM with direct LUN disk
I have a VM with a virtio-scsi disk that is a direct-mapped iSCSI LUN.
I'm trying to migrate it from one node to another (in the process of
updating my system from 3.5.3 to 3.5.5), and it fails migration with:
Thread-1886273::ERROR::2016-01-06 10:31:17,657::migration::161::vm.Vm::(_recover)
vmId=`606ae10e-bcac-4bf8-8ad0-e9d76f0c6f43`::unsupported configuration: scsi-block
'lun' devices do not support the serial property
Thread-1886273::ERROR::2016-01-06 10:31:17,693::migration::260::vm.Vm::(run)
vmId=`606ae10e-bcac-4bf8-8ad0-e9d76f0c6f43`::Failed to migrate
File "/usr/share/vdsm/virt/migration.py", line 246, in run
self._startUnderlyingMigration(time.time())
File "/usr/share/vdsm/virt/migration.py", line 335, in
_startUnderlyingMigration
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1701, in
migrateToURI2
if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed',
dom=self)
Thread-1886279::DEBUG::2016-01-06
10:31:18,539::__init__::481::jsonrpc.JsonRpcServer::(_serveRequest) Calling
'VM.getMigrationStatus' in bridge with {u'vmID':
u'606ae10e-bcac-4bf8-8ad0-e9d76f0c6f43'}
Is this a known bug (maybe fixed in a newer version), something
unexpected, etc.? Is there a way around it (other than shutting down
the VM)?
--
Chris Adams <cma(a)cmadams.net>