Hide Forgot
Description of problem: Migration intermittently fails with the error "Alias not found for device type graphics during migration at destination host" Version-Release number of selected component (if applicable): rhevm-3.5.3.1-1.4.el6ev.noarch vdsm-4.16.20-1.el7ev.x86_64 How reproducible: Unknown Steps to Reproduce: 1. Attempt to migrate a VM Actual results: Migration failed, with the following error in vdsm.log: Alias not found for device type graphics during migration at destination host Expected results: Successful migration Additional info:
please attach relevant engine, vdsm and libvirt (source host) logs
> Migration failed, with the following error in vdsm.log: > Alias not found for device type graphics during migration at destination host This is confusing and misleading - and indeed mislead the investigation here. Will fix in a low-priority patch.
(In reply to Francesco Romani from comment #8) > > Migration failed, with the following error in vdsm.log: > > Alias not found for device type graphics during migration at destination host > > This is confusing and misleading - and indeed mislead the investigation > here. Will fix in a low-priority patch. here: https://gerrit.ovirt.org/44669
Would you please add steps to reproduce?
(In reply to Ilanit Stein from comment #12) > Would you please add steps to reproduce? The only change we made to fix this bug was the removal of the misleading message as per https://bugzilla.redhat.com/show_bug.cgi?id=1248788#c9 to reproduce: - migrate any VM, verify the message "Alias not found for device type graphics" is present (hence the issue being addressed) on destination side - apply fix (or use fixed build) - migrate any VM, verify migration succeeds, graphic console works and message is gone
Verify with: RHEVM: rhevm-tools-3.6.0.3-0.1 vdsm:vdsm-4.17.10.1-0.el7ev libvirt: libvirt-1.2.17-13.el7 Scenario: 1. Migration VM 2. Check in vdsm.log the message in not on source / destination hosts and also in engine log. Results: Message not found in vdsm.log and engine.log
Since the fix was just about noise reduction in the logs, I don't think this feature deserves a mention in the docs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html