Using on source and target: - libvirt 6.0.0 Running: # virsh migrate --copy-storage-inc --verbose --persistent --live kvm1793 qemu+ssh://target-node/system will start successfully, and then during the migration, here in my case after 57% _might_ give: error: internal error: qemu unexpectedly closed the monitor: 2020-01-19T16:18:30.288906Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13] 2020-01-19T16:18:30.289800Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12] 2020-01-19T16:18:30.289827Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13] 2020-01-19T16:18:30.290706Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12] 2020-01-19T16:18:30.290734Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13] 2020-01-19T16:51:54.804831Z qemu-system-x86_64: Not a migration stream 2020-01-19T16:51:54.804906Z qemu-system-x86_64: load of migration failed: Invalid argument Running a second migration with the same command succeeded. Any idea whats causing this or at least the meaning of this ? The physical KVM hostmachines are identical in terms of CPU model. Thank you !
Hi, I'm seeing the same warnings about vmx-exit-load-perf-global-ctrl & vmx-entry-load-perf-global-ctrl but I doubt they are related to your migration issue. They are just emitted when qemu starts on the target but way before migration starts and you said you got to 57%. I've seen many those warnings when qemu/libvirt is newer than the kernel, since qemu tries to set sub-features but the kernel doesn't allow that yet. To avoid people trail a red herring and actually look into your migration issue I'd recommend disabling vmx for the guest which will make the warning disappear. Retrying the same again then will probably look the same (in case it was well-reproducible at all) minus these warnings.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.