<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 2, 2017 at 4:23 PM, Краснобаев Михаил <span dir="ltr"><<a href="mailto:milo1@ya.ru" target="_blank">milo1@ya.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi,</div><div> </div><div>upgraded my cluster (3 hosts, engine, nfs-share) to the latest 4.1 release and Centos 7.3 (from 4.06).</div><div> </div><div>Did the following:</div><div> </div><div>1. Upgraded engine machine to Centos 7.3</div><div>2. Upgraded engine packages and ran "engine-setup"</div><div>3. Upgraded one by one hosts to 7.3 + packages from the new 4.1. repo and refreshed hosts capabilities.</div><div>4. Raised cluster and datacenter compatibility level to 4.1.</div><div>5. Restarted virtual machines and tested migration.</div><div>6. Profit! Everything went really smoothly. No errors.</div><div> </div><div>Now trying to figure out how the sparsify function works. I need to run trimming from inside the VM first?</div></blockquote><div><br></div><div>If you've configured it to use virtio-SCSI, and DISCARD is enabled, you can. But I believe virt-sparsify does a bit.</div><div><br></div><div>BTW, depending on the OS, if DISCARD is enabled, I would not do anything - for example, in Fedora, there's a systemd timer that once a week runs fstrim for you.</div><div><br></div><div>If not, then it has to be turned off and then you can run virt-sparsify.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div> </div><div>Best regards, Mikhail.</div><div> </div><div> </div><div> </div><div>02.02.2017, 15:19, "Sandro Bonazzola" <<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>>:</div><blockquote type="cite"><div><div class="h5"><div>Hi,<div>did you install/update to 4.1.0? Let us know your experience!</div><div>We end up knowing only when things doesn't work well, let us know it works fine for you :-)</div><div> </div><div>If you're not planning an update to 4.1.0 in the near future, let us know why.</div><div>Maybe we can help.<div> </div><div>Thanks!</div>--<div><div><div><div><div><div><div><div>Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com/" target="_blank">redhat.com</a></div></div></div></div></div></div></div></div></div></div></div></div>,<p>______________________________<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></p></blockquote><span class="HOEnZb"><font color="#888888"><div> </div><div> </div><div>-- </div><div>С уважением, Краснобаев Михаил.</div><div> </div><div> </div></font></span><br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>