Karli, Almost everything can be updated without system reboot. Even kernel, see http://KernelCare.com/
From: Karli Sjöberg <ka...@inparadise.se> Date: Monday, 12 June 2017 at 20:35 To: Pavel Gashev <p...@acronis.com> Cc: Tomas Jelinek <tjeli...@redhat.com>, users <users@ovirt.org> Subject: Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1 Den 12 juni 2017 6:31 em skrev Pavel Gashev <p...@acronis.com>: Tomas, Since the restart is not actually required in my case, what if I set compatibility version in the DB directly to make the engine happy? I have no plans to restart my VMs in this year. Sorry for butting in, this has nothing to do with the subject but are you seriously _not_ going to the restart your VM's this year? If so, then how are you handling patching/upgrading of them? Because if you aren't, you are going to have bigger problems than we can help you with:) Just my two cents /K And I don’t want to block online updating of VM parameters by the “next run configuration”. From: Tomas Jelinek <tjeli...@redhat.com> Date: Monday, 12 June 2017 at 16:42 To: Pavel Gashev <p...@acronis.com> Cc: James <ja...@jloh.co>, users <users@ovirt.org> Subject: Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1 On Mon, Jun 12, 2017 at 2:12 PM, Pavel Gashev <p...@acronis.com<mailto: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<mailto:users-boun...@ovirt.org>> on behalf of Tomas Jelinek <tjeli...@redhat.com<mailto:tjeli...@redhat.com>> Date: Monday, 12 June 2017 at 14:15 To: James <ja...@jloh.co<mailto:ja...@jloh.co>> Cc: users <users@ovirt.org<mailto: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<mailto: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<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ 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
