On Mon, Jun 12, 2017 at 2:12 PM, Pavel Gashev <p...@acronis.com> wrote:
> Can I update VMs compatibility version without restarting VMs? > yes, but it will be applied only after restart. > > > According to the source code, restarting is required during upgrading to > 4.1 only if a VM uses random generator device. If it doesn’t, a restart is > not really required. > right, but the VM will still be marked with this "next run configuration" and will be set to have the old compatibility version. > > > > > *From: *<users-boun...@ovirt.org> on behalf of Tomas Jelinek < > tjeli...@redhat.com> > *Date: *Monday, 12 June 2017 at 14:15 > *To: *James <ja...@jloh.co> > *Cc: *users <users@ovirt.org> > *Subject: *Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1 > > > > > > > > On Mon, Jun 12, 2017 at 12:17 PM, James <ja...@jloh.co> wrote: > > We recently moved our oVirt cluster from 4.0 to 4.1 and have migrated > all the hosts. The datacenter currently has a compatability setting of > 4.1 but the cluster is still on 4.0. As cross-cluster migrations has > been removed (no option anymore?) we aren't 100% sure how to get the > cluster onto 4.1 whilst keeping the VMs online. Do we just change the > compatibility version live and it "just works" or do we have to have > downtime? > > > > yes, you just change the compatibility version. The VMs which are down > will be automatically updated and work with the new cluster, the running > ones will be marked with a "triangle" icon and will be automatically > updated on restart of them. > > > > > Any info would be great! > > Regards, > James > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > >
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
