<div dir='auto'><div><br><div class="gmail_extra"><br><div class="gmail_quote">Den 12 juni 2017 6:31 em skrev Pavel Gashev <Pax@acronis.com>:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div>
<p><span style="font-size:11pt;font-family:'calibri'">Tomas,</span></p>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<p><span style="font-size:11pt;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>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<p><span style="font-size:11pt;font-family:'calibri'">I have no plans to restart my VMs in this year.</span></p></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">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?</div><div dir="auto"><br></div><div dir="auto">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:)</div><div dir="auto"><br></div><div dir="auto">Just my two cents</div><div dir="auto"><br></div><div dir="auto">/K</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><p><span style="font-size:11pt;font-family:'calibri'"> And I don’t want to block online updating of VM parameters by the “next run configuration”.
</span></p>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<div style="border:none;border-top:solid #b5c4df 1pt;padding:3pt 0cm 0cm 0cm">
<p><b><span style="font-family:'calibri';color:black">From: </span>
</b><span style="font-family:'calibri';color:black">Tomas Jelinek <tjelinek@redhat.com><br>
<b>Date: </b>Monday, 12 June 2017 at 16:42<br>
<b>To: </b>Pavel Gashev <Pax@acronis.com><br>
<b>Cc: </b>James <james@jloh.co>, users <users@ovirt.org><br>
<b>Subject: </b>Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1</span></p>
</div>
<div>
<p> </p>
</div>
<div>
<p> </p>
<div>
<p> </p>
<div>
<p>On Mon, Jun 12, 2017 at 2:12 PM, Pavel Gashev <<a href="mailto:Pax@acronis.com">Pax@acronis.com</a>> wrote:</p>
<blockquote style="border:none;border-left:solid #cccccc 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p><span style="font-size:11pt;font-family:'calibri'">Can I update VMs compatibility version without restarting VMs?</span></p>
</div>
</div>
</blockquote>
<div>
<p> </p>
</div>
<div>
<p>yes, but it will be applied only after restart. </p>
</div>
<div>
<p> </p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<p><span style="font-size:11pt;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></p>
</div>
</div>
</blockquote>
<div>
<p> </p>
</div>
<div>
<p>right, but the VM will still be marked with this "next run configuration" and will be set to have the old compatibility version.</p>
</div>
<div>
<p> </p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<p><span style="font-size:11pt;font-family:'calibri'"> </span></p>
<div style="border:none;border-top:solid #b5c4df 1pt;padding:3pt 0cm 0cm 0cm">
<p><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">users-bounces@ovirt.org</a>> on behalf of Tomas Jelinek <<a href="mailto:tjelinek@redhat.com">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">james@jloh.co</a>><br>
<b>Cc: </b>users <<a href="mailto:users@ovirt.org">users@ovirt.org</a>><br>
<b>Subject: </b>Re: [ovirt-users] Migrating oVirt cluster from 4.0 to 4.1</span></p>
</div>
<div>
<div>
<div>
<p> </p>
</div>
<div>
<p> </p>
<div>
<p> </p>
<div>
<p>On Mon, Jun 12, 2017 at 12:17 PM, James <<a href="mailto:james@jloh.co">james@jloh.co</a>> wrote:</p>
<blockquote style="border:none;border-left:solid #cccccc 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-top:5pt;margin-right:0cm;margin-bottom:5pt">
<p>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?</p>
</blockquote>
<div>
<p> </p>
</div>
<div>
<p>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.</p>
</div>
<div>
<p> </p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-top:5pt;margin-right:0cm;margin-bottom:5pt">
<p><br>
Any info would be great!<br>
<br>
Regards,<br>
James<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a></p>
</blockquote>
</div>
<p> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p> </p>
</div>
</div>
</div>
<br><br>_______________________________________________
<br>Users mailing list
<br>Users@ovirt.org
<br>http://lists.ovirt.org/mailman/listinfo/users
<br></div>
</blockquote></div><br></div></div></div>