On Mon, Dec 5, 2016 at 10:25 PM, Marcelo Leandro <marceloltmm@gmail.com> wrote:
Hello I am with problem, I can not migrate vm. Can someone help me?
Message in log:
Src vdsm log:
Thread-89514 :: WARNING :: 2016-12-05 17: 01: 49,542 :: migration :: 683 :: virt.vm ::: monitor_migration vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: Migration Stalling: remaining (56MiB)> lowmark (2MiB). Refer to RHBZ # 919201. Thread-89514 :: DEBUG :: 2016-12-05 17: 01: 49,543 :: migration :: 689 :: virt.vm ::: monitor_migration vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: new Iteration detected: 15 Thread-89514 :: WARNING :: 2016-12-05 17: 01: 49,543 :: migration :: 704 :: virt.vm ::: monitor_migration vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: Migration Is stuck: Has not pro Gressed in 240.071660042 seconds. Aborting.
This is usually a result of a too-busy VM, changing its memory faster than the migration process can copy the changes to the destination. You can try changing the cluster migration policy to "suspend workload if needed". For more details/background, see also: https://www.ovirt.org/develop/release-management/features/migration-enhancem... Best,
Thread-89514 :: DEBUG :: 2016-12-05 17: 01: 49,544 :: migration :: 715 :: virt.vm ::: stop} vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: stopping Migration monitor thread Thread-89514 :: DEBUG :: 2016-12-05 17: 01: 49,545 :: migration :: 570 :: virt.vm ::: stop) vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: stopping Migration downtime thread Thread-89514 :: DEBUG :: 2016-12-05 17: 01: 49,545 :: migration :: 629 :: virt.vm ::: (run) vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: stopped Migration monitor thread Thread-89513 :: DEBUG :: 2016-12-05 17: 01: 49,766 :: migration :: 715 :: virt.vm ::: stop} vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: stopping Migration monitor thread Thread-89513 :: ERROR :: 2016-12-05 17: 01: 49,767 :: migration :: 252 :: virt.vm :: (_ recover) vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: operation Aborted: migration job: cancel D by cliente
Dst vdsm.log:
Periodic / 13 :: WARNING :: 2016-12-05 17: 01: 49,791 :: sampling :: 483 :: virt.sampling.StatsCache: :( put) dropped stale old sample: sampled 4303678.080000 stored 4303693.070000 Periodic / 13 :: DEBUG :: 2016-12-05 17: 01: 49,791 :: executor :: 221 :: Executor :: (_ run) Worker was discarded Jsonrpc.Executor / 0 :: DEBUG :: 2016-12-05 17: 01: 49,792 :: __ init __ :: 530 :: jsonrpc.JsonRpcServer :: (_ handle_request) Calling 'VM.destroy' in bridge with {u'vmID ' : U'f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e '} Jsonrpc.Executor / 0 :: DEBUG :: 2016-12-05 17: 01: 49,793 :: API :: 314 :: vds :::( destroy) About to destroy VM f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e Jsonrpc.Executor / 0 :: DEBUG :: 2016-12-05 17:01:49,793 :: vm :: 4171 :: virt.vm :::( destroy) vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e`: : Destroy Called Thread-483 :: ERROR :: 2016-12-05 17: 01: 49,793 :: vm :: 759 :: virt.vm :: (_ startUnderlyingVm) vmId = `f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e` :: Failed To start a migration destination vm Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 725, in _startUnderlyingVm Self._completeIncomingMigration () File "/usr/share/vdsm/virt/vm.py", line 3071, in _completeIncomingMigration Self._incomingMigrationFinished.isSet (), usedTimeout) File "/usr/share/vdsm/virt/vm.py", line 3154, in _attachLibvirtDomainAfterMigration Raise MigrationError (e.get_error_message ()) MigrationError: Domain not found: no domain with matching uuid 'f38b9f7d-5bd0-4bdf-885c-e03e8d6bc70e'
The logs attached. Thanks.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Didi