Re: [ovirt-users] Error migrating VM with direct LUN disk
Once upon a time, Yedidyah Bar David said: > On Thu, Jan 7, 2016 at 10:16 AM, Chris Adams wrote: > > Once upon a time, Chris Adams said: > >> 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)? > > > > So, this isn't just a bug with migration; I powered off the VM and then > > tried to start it on a host that had been updated to 3.5.5 and it would > > not start (same error). > > > > This is a pretty significant regression IMHO - I can't start this VM on > > any 3.5.5 host. > > Seems like a result of the fix for [1]. > > Please check/post vdsm/libvirt/qemu versions and logs. Old node (that is working) is CentOS 7.1, oVirt 3.5.3: vdsm-4.16.20-0.el7.centos.x86_64 libvirt-client-1.2.8-16.el7_1.3.x86_64 qemu-kvm-ev-2.1.2-23.el7_1.3.1.x86_64 New nodes (that won't work) are CentOS 7.2, oVirt 3.5.6 (I said 3.5.5 earlier but they are updated as of yesterday): vdsm-4.16.30-0.el7.centos.x86_64 libvirt-client-1.2.17-13.el7_2.2.x86_64 qemu-kvm-ev-2.3.0-29.1.el7.x86_64 Please let me know which logs - the above snip is from vdsm.log when trying to migrate the VM (got the same error when just trying to start it). All that is in the libvirt/qemu/.log when I tried to start the VM on an upgraded node is "shutting down" (no errors or other messages). > Do you have any vdsm hooks installed? No. I did wonder if I could work around this with a hook to strip out the in the XML (but haven't written a hook before so haven't tried that yet). > Was this system upgraded from a previous version? Please > state the upgrade history. It started with either 3.5 or 3.5.1 (can't remember for sure now), then upgraded to 3.5.2, 3.5.3, and 3.5.6. > Thanks. Thank you. -- Chris Adams ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Error migrating VM with direct LUN disk
On Thu, Jan 7, 2016 at 10:16 AM, Chris Adams wrote: > Once upon a time, Chris Adams said: >> 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)? > > So, this isn't just a bug with migration; I powered off the VM and then > tried to start it on a host that had been updated to 3.5.5 and it would > not start (same error). > > This is a pretty significant regression IMHO - I can't start this VM on > any 3.5.5 host. Seems like a result of the fix for [1]. Please check/post vdsm/libvirt/qemu versions and logs. Do you have any vdsm hooks installed? Was this system upgraded from a previous version? Please state the upgrade history. Thanks. Adding Allon. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1021480 > -- > Chris Adams > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Error migrating VM with direct LUN disk
Can you please add logs? Yaniv Dary Technical Product Manager Red Hat Israel Ltd. 34 Jerusalem Road Building A, 4th floor Ra'anana, Israel 4350109 Tel : +972 (9) 7692306 8272306 Email: yd...@redhat.com IRC : ydary On Thu, Jan 7, 2016 at 10:16 AM, Chris Adams wrote: > Once upon a time, Chris Adams said: > > 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)? > > So, this isn't just a bug with migration; I powered off the VM and then > tried to start it on a host that had been updated to 3.5.5 and it would > not start (same error). > > This is a pretty significant regression IMHO - I can't start this VM on > any 3.5.5 host. > -- > Chris Adams > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Error migrating VM with direct LUN disk
Once upon a time, Chris Adams said: > 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)? So, this isn't just a bug with migration; I powered off the VM and then tried to start it on a host that had been updated to 3.5.5 and it would not start (same error). This is a pretty significant regression IMHO - I can't start this VM on any 3.5.5 host. -- Chris Adams ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users