Created attachment 948263 [details] engine logs check with vesion: 3.5.0-0.12.beta.el6ev How reproducible: 1. RHEL 6.5 VM with Defined Memory: 2G 2. 2 Hosts 3. On migrate VM runnnig linux stress with command: stress --vm 1 --vm-bytes 512M --vm-hang 2 --timeout 3600s & 4. Migrate VM via UI 5. The migrate failed after ~2 min, in the event tab the message was: 2014-Oct-19, 14:40 Migration failed due to Error: Migration not in progress (VM: test-02, Source: 10.35.4.161, Destination: 10.35.4.137). Actual results: No explanation why the migrate failed. Expected results: Explanation why the migrate failed: Timeout. Additional info: * From the vdsm log: Thread-75::WARNING::2014-10-19 14:40:35,602::migration::435::vm.Vm::(monitor_migration) vmId=`6b3cd572-a7ce-4775-b405-4eb53e7a0968`::The migration took 130 seconds which is exceeding the configured maximum time for migrations of 128 seconds. The migration will be aborted. The migrate failed since timeout. *See attached logs.
Created attachment 948264 [details] Host Logs
migration reporting improvement
VDSM patch posted. Not sure this is better handled on VDSM side or on Engine side. Let's discuss on gerrit.
https://bugzilla.redhat.com/show_bug.cgi?id=1134974 is related, probably same (or very similar) root cause
fixing in vdsm might be more complicated than fixing in engine, suggestion is that on migration failure, engine will query both src and dst hosts for the failure reason (instead of the current way of querying only the src) and provide better info to the user. this will not make it on time for 3.6.0 suggesting 3.6.z because this can improve user experience, but anyway the failure reason is available manually for the user on the hosts.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
will not fit into 4.0 - pushing to 4.1
There is no simple/good solution to this. The previous patches have been abandoned. Considering the changes in migration in 4.0 and the adding of the postcopy in 4.1 I think this is not relevant anymore, so closing. If you will face this and is important to you, please feel free to reopen.