Created attachment 939371 [details] qemu log file from one host, there were both successful and unsuccessful attempts there (both ways) so you can compare Description of problem: When a migration is attempted, qemu on the destination dies almost immediately. Version-Release number of selected component (if applicable): Both source and destination are identical: F19 qemu-1.6.1-2.fc19 libvirt-python-1.1.3.2-1.fc19.x86_64 vdsm-4.14.11.2-0.fc19.x86_64 How reproducible: Always on my setup. The error goes away when I disable virtio-scsi. Steps to Reproduce: 1. Start a VM (I use oVirt engine to do that) 2. Initiate migration 3. Watch the crash Actual results: VM on destination crashes Expected results: VM migrates. Additional info:
Quite an old version of qemu here. F19 is going to be out of support in about 2-3 months (1 month after we manage to get F21 out). Can you upgrade?
Unfortunately we still support oVirt on F19. And I was not able to migrate on F20 (with virt preview) either, but I do not have enough hosts to try to reproduce atm. We are using virt preview to get new libvirt.
Does the ovirt version in stock fedora 19 require the libvirt version from virt-preview? If so, you guys are in a pickle. Fedora 19 virt-preview is no longer updated, it stopped updating the second Fedora 20 came out. So I'd recommend downgrading to stock fedora 19 packages if that's an option, since they are likely more stable at this point than an outdated snapshot of virt-preview packages.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.