subject:"\[ovirt\-users\] Re\: migration failed"

[ovirt-users] Re: migration failed

2019-01-01 Thread Michal Skrivanek



> On 2 Jan 2019, at 03:02, 董青龙  wrote:
> 
> Hi all,
> I have an ovirt4.2 environment of 3 hosts. Now all vms in this 
> environment could not be migrated. But all the vms could be started on all 3 
> hosts. Anyone can help? Thanks a lot!

can you add source and destination vdsm.log please?

> 
> engine logs:
> 
> 2019-01-02 09:41:26,868+08 INFO  [org.ovirt.engine.core.bll.MigrateVmCommand] 
> (default task-9) [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] Lock Acquired to 
> object 
> 'EngineLock:{exclusiveLocks='[eff7f697-8a07-46e5-a631-a1011a0eb836=VM]', 
> sharedLocks=''}'
> 2019-01-02 09:41:26,978+08 INFO  [org.ovirt.engine.core.bll.MigrateVmCommand] 
> (EE-ManagedThreadFactory-engine-Thread-168938) 
> [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] Running command: MigrateVmCommand 
> internal: false. Entities affected :  ID: 
> eff7f697-8a07-46e5-a631-a1011a0eb836 Type: VMAction group MIGRATE_VM with 
> role type USER
> 2019-01-02 09:41:27,019+08 INFO  
> [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-168938) 
> [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] START, MigrateVDSCommand( 
> MigrateVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', 
> vmId='eff7f697-8a07-46e5-a631-a1011a0eb836', srcHost='horeb66', 
> dstVdsId='5bb18f6e-9c7e-4afd-92de-f6482bf752e5', dstHost='horeb65:54321', 
> migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', 
> autoConverge='true', migrateCompressed='false', consoleAddress='null', 
> maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', 
> maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, 
> params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, 
> {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, 
> action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, 
> params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, 
> {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.128.78'}), 
> log id: 1bd72db2
> 2019-01-02 09:41:27,019+08 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-168938) 
> [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] START, 
> MigrateBrokerVDSCommand(HostName = horeb66, 
> MigrateVDSCommandParameters:{hostId='0aff0075-4b41-4f37-98de-7433a17cd47e', 
> vmId='eff7f697-8a07-46e5-a631-a1011a0eb836', srcHost='horeb66', 
> dstVdsId='5bb18f6e-9c7e-4afd-92de-f6482bf752e5', dstHost='horeb65:54321', 
> migrationMethod='ONLINE', tunnelMigration='false', migrationDowntime='0', 
> autoConverge='true', migrateCompressed='false', consoleAddress='null', 
> maxBandwidth='500', enableGuestEvents='true', maxIncomingMigrations='2', 
> maxOutgoingMigrations='2', convergenceSchedule='[init=[{name=setDowntime, 
> params=[100]}], stalling=[{limit=1, action={name=setDowntime, params=[150]}}, 
> {limit=2, action={name=setDowntime, params=[200]}}, {limit=3, 
> action={name=setDowntime, params=[300]}}, {limit=4, action={name=setDowntime, 
> params=[400]}}, {limit=6, action={name=setDowntime, params=[500]}}, 
> {limit=-1, action={name=abort, params=[]}}]]', dstQemu='192.168.128.78'}), 
> log id: 380b8d38
> 2019-01-02 09:41:27,025+08 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateBrokerVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-168938) 
> [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] FINISH, MigrateBrokerVDSCommand, log 
> id: 380b8d38
> 2019-01-02 09:41:27,029+08 INFO  
> [org.ovirt.engine.core.vdsbroker.MigrateVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-168938) 
> [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] FINISH, MigrateVDSCommand, return: 
> MigratingFrom, log id: 1bd72db2
> 2019-01-02 09:41:27,036+08 INFO  
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-168938) 
> [3eed5f0e-aaf5-4dce-bf30-2c49e09ab30d] EVENT_ID: VM_MIGRATION_START(62), 
> Migration started (VM: win7, Source: horeb66, Destination: horeb65, User: 
> admin@internal-authz). 
> 2019-01-02 09:41:41,557+08 INFO  
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] VM 
> 'eff7f697-8a07-46e5-a631-a1011a0eb836'(win7) moved from 'MigratingFrom' --> 
> 'Up'
> 2019-01-02 09:41:41,557+08 INFO  
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] Adding VM 
> 'eff7f697-8a07-46e5-a631-a1011a0eb836'(win7) to re-run list
> 2019-01-02 09:41:41,567+08 ERROR 
> [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-30) [] Rerun VM 
> 'eff7f697-8a07-46e5-a631-a1011a0eb836'. Called from VDS 'horeb66'
> 2019-01-02 09:41:41,570+08 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.MigrateStatusVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-168945) [] START, 
> MigrateStatusVDSCommand(HostName = horeb66, 
> Migr

[ovirt-users] Re: Migration failed due to an Error: Fatal error during migration

2022-01-25 Thread Sandro Bonazzola

Hi, can you please provide versions of the non-upgraded hosts, of the
upgraded hosts  (I'm assuming you are using oVirt Node, if not, please
provide the reports form `sos report -o rpm
`) and of the engine?

Il giorno mar 25 gen 2022 alle ore 02:49 Gunasekhar Kothapalli via Users <
users@ovirt.org> ha scritto:

>
> I am able to power on vms on newly upgraded host, But not able to migrate
> VMs from other
> hosts to new host or newly upgraded hosts to other hosts. This was worked
> fine before
> upgraded.
>
> Host logs
>
> ==
> Unable to read from monitor: Connection reset by peer
> internal error: qemu unexpectedly closed the monitor:
> 2022-01-24T17:51:46.598571Z
> qemu-kvm: get_pci_config_device: Bad config >
> 2022-01-24T17:51:46.598627Z qemu-kvm: Failed to load PCIDevice:config
> 2022-01-24T17:51:46.598635Z qemu-kvm: Failed to load
> pcie-root-port:parent_obj.parent_obj.parent_obj
> 2022-01-24T17:51:46.598642Z qemu-kvm: error while loading state for
> instance 0x0 of device
> ':00:02.0/pcie-root-port'
> 2022-01-24T17:51:46.598830Z qemu-kvm: load of migration failed: Invalid
> argument
> Guest agent is not responding: QEMU guest agent is not connected
> Guest agent is not responding: QEMU guest agent is not connected
> Guest agent is not responding: QEMU guest agent is not connected
>
> Engine Logs
> ===
>
> 2022-01-24 11:31:25,080-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-21) [] Adding VM
> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list
> 2022-01-24 11:31:25,099-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-2331914) [] EVENT_ID:
> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal
> error during migration (VM: zzz2019, Source:
> lcoskvmp07.cos.is.keysight.com, Destination:
> lcoskvmp03.cos.is.keysight.com).
> 2022-01-24 18:39:47,897-07 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-771) [a78e85d4-068a-41c1-a8fa-b3acd8c69317] EVENT_ID:
> VM_MIGRATION_START(62), Migration started (VM: zzz2019, Source:
> lcoskvmp07.cos.is.keysight.com, Destination:
> lcoskvmp03.cos.is.keysight.com, User: k.gunasek...@non.keysight.com
> @KEYSIGHT).
> 2022-01-24 18:40:01,417-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-27) [] VM
> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected
> as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(
> lcoskvmp03.cos.is.keysight.com) (expected on
> '0d58953f-b3cc-4bac-b3b2-08ba1bca')
> 2022-01-24 18:40:01,589-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-27) [] VM
> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected
> as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(
> lcoskvmp03.cos.is.keysight.com) (expected on
> '0d58953f-b3cc-4bac-b3b2-08ba1bca')
> 2022-01-24 18:40:01,589-07 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-27) [] Migration of VM 'zzz2019' to host '
> lcoskvmp03.cos.is.keysight.com' failed: VM destroyed during the startup.
> 2022-01-24 18:40:01,591-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-17) [] VM
> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) moved from 'MigratingFrom'
> --> 'Up'
> 2022-01-24 18:40:01,591-07 INFO
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
> (ForkJoinPool-1-worker-17) [] Adding VM
> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list
> 2022-01-24 18:40:01,611-07 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-2348837) [] EVENT_ID:
> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal
> error during migration (VM: zzz2019, Source:
> lcoskvmp07.cos.is.keysight.com, Destination:
> lcoskvmp03.cos.is.keysight.com).
> [root@lcosovirt02 ovirt-engine]#
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2W5OEBPZM3TLS3P6DXPWWKNU5SPPEGAD/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...

[ovirt-users] Re: Migration failed due to an Error: Fatal error during migration

2022-01-25 Thread Liran Rotenberg

On Tue, Jan 25, 2022 at 10:36 AM Sandro Bonazzola 
wrote:

> Hi, can you please provide versions of the non-upgraded hosts, of the
> upgraded hosts  (I'm assuming you are using oVirt Node, if not, please
> provide the reports form `sos report -o rpm
> `) and of the engine?
>
> Il giorno mar 25 gen 2022 alle ore 02:49 Gunasekhar Kothapalli via Users <
> users@ovirt.org> ha scritto:
>
>>
>> I am able to power on vms on newly upgraded host, But not able to migrate
>> VMs from other
>> hosts to new host or newly upgraded hosts to other hosts. This was worked
>> fine before
>> upgraded.
>>
>> Host logs
>>
>> ==
>> Unable to read from monitor: Connection reset by peer
>> internal error: qemu unexpectedly closed the monitor:
>> 2022-01-24T17:51:46.598571Z
>> qemu-kvm: get_pci_config_device: Bad config >
>> 2022-01-24T17:51:46.598627Z qemu-kvm: Failed to load PCIDevice:config
>> 2022-01-24T17:51:46.598635Z qemu-kvm: Failed to load
>> pcie-root-port:parent_obj.parent_obj.parent_obj
>> 2022-01-24T17:51:46.598642Z qemu-kvm: error while loading state for
>> instance 0x0 of device
>> ':00:02.0/pcie-root-port'
>> 2022-01-24T17:51:46.598830Z qemu-kvm: load of migration failed: Invalid
>> argument
>> Guest agent is not responding: QEMU guest agent is not connected
>> Guest agent is not responding: QEMU guest agent is not connected
>> Guest agent is not responding: QEMU guest agent is not connected
>>
>> Engine Logs
>> ===
>>
>> 2022-01-24 11:31:25,080-07 INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-21) [] Adding VM
>> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list
>> 2022-01-24 11:31:25,099-07 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engine-Thread-2331914) [] EVENT_ID:
>> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal
>> error during migration (VM: zzz2019, Source:
>> lcoskvmp07.cos.is.keysight.com, Destination:
>> lcoskvmp03.cos.is.keysight.com).
>> 2022-01-24 18:39:47,897-07 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-771) [a78e85d4-068a-41c1-a8fa-b3acd8c69317] EVENT_ID:
>> VM_MIGRATION_START(62), Migration started (VM: zzz2019, Source:
>> lcoskvmp07.cos.is.keysight.com, Destination:
>> lcoskvmp03.cos.is.keysight.com, User: k.gunasek...@non.keysight.com
>> @KEYSIGHT).
>> 2022-01-24 18:40:01,417-07 INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-27) [] VM
>> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected
>> as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(
>> lcoskvmp03.cos.is.keysight.com) (expected on
>> '0d58953f-b3cc-4bac-b3b2-08ba1bca')
>> 2022-01-24 18:40:01,589-07 INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-27) [] VM
>> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) was unexpectedly detected
>> as 'Down' on VDS 'ee23b44d-976d-4889-8769-59b56e4b23c0'(
>> lcoskvmp03.cos.is.keysight.com) (expected on
>> '0d58953f-b3cc-4bac-b3b2-08ba1bca')
>> 2022-01-24 18:40:01,589-07 ERROR
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-27) [] Migration of VM 'zzz2019' to host '
>> lcoskvmp03.cos.is.keysight.com' failed: VM destroyed during the startup.
>> 2022-01-24 18:40:01,591-07 INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-17) [] VM
>> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) moved from 'MigratingFrom'
>> --> 'Up'
>> 2022-01-24 18:40:01,591-07 INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (ForkJoinPool-1-worker-17) [] Adding VM
>> '9838c44b-710f-407a-b775-56bb0a3d4221'(zzz2019) to re-run list
>> 2022-01-24 18:40:01,611-07 ERROR
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (EE-ManagedThreadFactory-engine-Thread-2348837) [] EVENT_ID:
>> VM_MIGRATION_TO_SERVER_FAILED(120), Migration failed due to an Error: Fatal
>> error during migration (VM: zzz2019, Source:
>> lcoskvmp07.cos.is.keysight.com, Destination:
>> lcoskvmp03.cos.is.keysight.com).
>> [root@lcosovirt02 ovirt-engine]#
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/2W5OEBPZM3TLS3P6DXPWWKNU5SPPEGAD/
>>
>
> Hi,
I answered on the other thread. This is a known problem with qemu-kvm 6.1.
Please try to downgrade to 6.0.
Regards,
Liran

>
> --
>
> Sandro Bonazzola
>
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>
> Red Hat EMEA

[ovirt-users] Re: Migration failed due to an Error: Fatal error during migration

2022-01-25 Thread Gunasekhar Kothapalli via Users

This helped to resolve the issue. thank you
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BLV4B5NKRWKZHQHK64LF6LLFKP4CIREQ/

[ovirt-users] Re: migration failed

[ovirt-users] Re: Migration failed due to an Error: Fatal error during migration

[ovirt-users] Re: Migration failed due to an Error: Fatal error during migration

[ovirt-users] Re: Migration failed due to an Error: Fatal error during migration

4 matches

Site Navigation

Mail list logo

Footer information