<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 12, 2017 at 6:30 PM, Pavel Gashev <span dir="ltr"><<a href="mailto:Pax@acronis.com" target="_blank">Pax@acronis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple" lang="EN-GB">
<div class="m_-1231520090022833277WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Tomas,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">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?</span></p></div></div></blockquote><div><br></div><div>that's a nasty hack... <br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" link="blue" vlink="purple" lang="EN-GB"><div class="m_-1231520090022833277WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I have no plans to restart my VMs in this year. And I don’t want to block online updating of VM parameters by the “next run configuration”.
</span></p></div></div></blockquote><div><br></div><div>By online updating you mean hotplug? Or just normal update of fields which don't need restart (like description)? Because both are possible even with a next run snapshot.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="white" link="blue" vlink="purple" lang="EN-GB"><div class="m_-1231520090022833277WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Tomas Jelinek <<a href="mailto:tjelinek@redhat.com" target="_blank">tjelinek@redhat.com</a>><br>
<b>Date: </b>Monday, 12 June 2017 at 16:42<br>
<b>To: </b>Pavel Gashev <<a href="mailto:Pax@acronis.com" target="_blank">Pax@acronis.com</a>><br>
<b>Cc: </b>James <<a href="mailto:james@jloh.co" target="_blank">james@jloh.co</a>>, users <<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>></span></p><div><div class="h5"><br>
<b>Subject: </b>Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1<u></u><u></u></div></div><p></p>
</div><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Mon, Jun 12, 2017 at 2:12 PM, Pavel Gashev <<a href="mailto:Pax@acronis.com" target="_blank">Pax@acronis.com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Can I update VMs compatibility version without restarting VMs?</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">yes, but it will be applied only after restart. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">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.</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">right, but the VM will still be marked with this "next run configuration" and will be set to have the old compatibility version.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"> </span><u></u><u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From:
</span></b><span style="font-family:Calibri;color:black"><<a href="mailto:users-bounces@ovirt.org" target="_blank">users-bounces@ovirt.org</a>> on behalf of Tomas Jelinek <<a href="mailto:tjelinek@redhat.com" target="_blank">tjelinek@redhat.com</a>><br>
<b>Date: </b>Monday, 12 June 2017 at 14:15<br>
<b>To: </b>James <<a href="mailto:james@jloh.co" target="_blank">james@jloh.co</a>><br>
<b>Cc: </b>users <<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>><br>
<b>Subject: </b>Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1</span><u></u><u></u></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">On Mon, Jun 12, 2017 at 12:17 PM, James <<a href="mailto:james@jloh.co" target="_blank">james@jloh.co</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<p class="MsoNormal">We recently moved our oVirt cluster from 4.0 to 4.1 and have migrated<br>
all the hosts. The datacenter currently has a compatability setting of<br>
4.1 but the cluster is still on 4.0. As cross-cluster migrations has<br>
been removed (no option anymore?) we aren't 100% sure how to get the<br>
cluster onto 4.1 whilst keeping the VMs online. Do we just change the<br>
compatibility version live and it "just works" or do we have to have<br>
downtime?<u></u><u></u></p>
</blockquote>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt">
<p class="MsoNormal"><br>
Any info would be great!<br>
<br>
Regards,<br>
James<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div></div></div>
</div>
</blockquote></div><br></div></div>