> On 23 Feb 2017, at 17:08, Michael Watters <[email protected]> wrote: > > I canceled the migration and manually moved the VM to another host > running ovirt 4.0. The source node was then able to set itself to > maintenance mode without any errors. > > On 02/23/2017 10:46 AM, Michael Watters wrote: >> >> On 02/23/2017 10:28 AM, Francesco Romani wrote: >>> The load/save state errors are most often found when the two sides of >>> the migration have different and incompatible version of QEMU. >>> In turn, this is quite often a bug, because forward migrations (e.g. >>> from 2.3.0 to 2.4.0) are always supported, for obvious upgrade needs. >> I think you're on to something there. The destination server is running >> ovirt 3.6 while the source server is on 4.0. The cluster compatibility >> level is also set to 3.6 since I have not upgrade every host node yet.
that is supported and works when the versions are really the latest ones. I suggest to check the repos, it might be you are not getting updates for CentOS or qemu-kvm-ev packages on either 3.6 or 4.0 side >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ovirt.org/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
