On 03/24/2017 11:58 AM, Davide Ferrari wrote: > And this is the vdsm log from vmhost04: > > Thread-6320717::INFO::2017-03-24 > 11:41:13,019::migration::712::virt.vm::(monitor_migration) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::Migration Progress: 190 > seconds elapsed, 98% of data processed, total data: 16456MB, processed > data: 9842MB, remaining data: 386MB, transfer speed 52MBps, zero > pages: 1718676MB, compressed: 0MB, dirty rate: -1, memory iteration: -1 > libvirtEventLoop::DEBUG::2017-03-24 > 11:41:21,007::vm::4291::virt.vm::(onLibvirtLifecycleEvent) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::event Suspended detail 0 > opaque None > libvirtEventLoop::INFO::2017-03-24 > 11:41:21,025::vm::4815::virt.vm::(_logGuestCpuStatus) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::CPU stopped: onSuspend > libvirtEventLoop::DEBUG::2017-03-24 > 11:41:21,069::vm::4291::virt.vm::(onLibvirtLifecycleEvent) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::event Resumed detail 0 > opaque None > libvirtEventLoop::INFO::2017-03-24 > 11:41:21,069::vm::4815::virt.vm::(_logGuestCpuStatus) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::CPU running: onResume > Thread-6320715::DEBUG::2017-03-24 > 11:41:21,224::migration::715::virt.vm::(stop) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::stopping migration > monitor thread > Thread-6320715::ERROR::2017-03-24 > 11:41:21,225::migration::252::virt.vm::(_recover) > vmId=`4f627cc1-9b52-4eef-bf3a-c02e8a6303b8`::operation failed: > migration job: unexpectedly failed
This is surprising (no pun intended) With a pretty high chance this comes from libvirt, I'm afraid you need to dig in the libvirt logs/journal entries to learn more. Vdsm could unfortunately do better than what it is already doing :\ -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
