<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 9, 2017 at 4:46 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 9, 2017 at 4:11 PM, <span dir="ltr"><<a href="mailto:ovirt@timmi.org" target="_blank">ovirt@timmi.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
Hi Gianluca,<br>
<br>
I tried to clone the VM but it does not help. It is still thin
allocation.<br>
<br>
Best regards<br>
Christoph<div><div class="m_6832984903494034171gmail-h5"><br><br>
</div></div></div>
</blockquote></div><br></div></span><div class="gmail_extra">Hi,</div><div class="gmail_extra">I referred to this information for the clone of VM scenario:</div><div class="gmail_extra"><a href="http://lists.ovirt.org/pipermail/users/2016-May/040129.html" target="_blank">http://lists.ovirt.org/<wbr>pipermail/users/2016-May/<wbr>040129.html</a><br></div><div class="gmail_extra">that contains:</div><div class="gmail_extra"><br></div><div class="gmail_extra">"</div><div class="gmail_extra"><div class="gmail_extra">>What happens if you clone a source VM which is using "thin" ?</div><div class="gmail_extra">The VM cloned from a thin templated base VM will be created with a full</div><div class="gmail_extra">copy of the disk (as in "Clone" when creating from template)</div><div>"<br></div><div>but I have not tried myself recently with 4.0/4.1 versions<br></div><div><br></div><div>Instead I did test some days ago with 4.0.6 this scenario below as I wanted to convert a source thin provisioned VM to a preallocated template:</div><div>VM is powered on</div><div>create a snapshot of the VM</div><div>select the snapshot line and select clone</div><div>in resource allocation section of the new vm screen change allocation policy for the desired disk/s from thin provision to preallocated</div><div>Then you can decommission old VM and use the cloned one</div><div>Verified today in 4.1 too.<br></div><div><br></div><div>Or from the snapshot line you can also "make template" if you plan to use it as a base for more VMs.</div><div>But in this case (tested in 4.1) your options are shown in a "Format" column, not "Allocation Policy" column; and you can choose between QCOW2 (that should be thin) and Raw (that should be preallocated).</div><div>See my screenshot:</div><div><a href="https://drive.google.com/file/d/0BwoPbcrMv8mvTHIzTU5kdHVJOG8/view?usp=sharing" target="_blank">https://drive.google.com/file/<wbr>d/<wbr>0BwoPbcrMv8mvTHIzTU5kdHVJOG8/<wbr>view?usp=sharing</a><br></div><div>Probably it should be made consistent and show "Allocation Policy" instead and related values?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Gianluca</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></font></span></div></div></blockquote><div><br></div><div>Hi,<br></div><div>I just tested this on 4.1:<br></div><div>- take a VM with a thin provisioned disk<br></div><div>How to see allocation policy?<br></div><div>It seems suboptimal for me: I would expect to see this kind of information in disks sub pane of the vm.<br></div><div>Instead I have to select snaphsots sub pane, then for example the "Current' line, and at the right side sub pane in disks tab I see "Allocation Policy" - thin provision<br><br></div><div>- make a clone of it in a new VM<br></div><div>In the same sub pane for the new VM I see preallocated.... so it seems to work as I read<br></div><div>This is on FC-SAN. What kind of storage is yours?<br> <br></div></div><br></div></div>