Hi oVirt List, I'm trying to change the disk allocation policy of a VM disk and I'm not able to perform this task via the oVirt front-end. Is someone able to tell me how I can do that? Best regards and thank you Christoph
On Thu, Feb 9, 2017 at 3:06 PM, <ovirt@timmi.org> wrote:
Hi oVirt List,
I'm trying to change the disk allocation policy of a VM disk and I'm not able to perform this task via the oVirt front-end.
Is someone able to tell me how I can do that?
Best regards and thank you Christoph
I've done it in the past by creating a snapshot of a VM and then cloning the snapshot and selecting preallocated for the cloned disks (if you have to do it without powering off the source VM) Or directly creating a clone of the VM if it is powered off, I think it creates a full preallocated copy and btw you have no way to tell to clone as thin if I remember correctly Gianluca
This is a multi-part message in MIME format. --------------6286BDE16222262E5DB9D903 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Gianluca, I tried to clone the VM but it does not help. It is still thin allocation. Best regards Christoph Am 09.02.2017 um 15:44 schrieb Gianluca Cecchi:
On Thu, Feb 9, 2017 at 3:06 PM, <ovirt@timmi.org <mailto:ovirt@timmi.org>> wrote:
Hi oVirt List,
I'm trying to change the disk allocation policy of a VM disk and I'm not able to perform this task via the oVirt front-end.
Is someone able to tell me how I can do that?
Best regards and thank you Christoph
I've done it in the past by creating a snapshot of a VM and then cloning the snapshot and selecting preallocated for the cloned disks (if you have to do it without powering off the source VM) Or directly creating a clone of the VM if it is powered off, I think it creates a full preallocated copy and btw you have no way to tell to clone as thin if I remember correctly
Gianluca
--------------6286BDE16222262E5DB9D903 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> 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<br> <br> <div class="moz-cite-prefix">Am 09.02.2017 um 15:44 schrieb Gianluca Cecchi:<br> </div> <blockquote cite="mid:CAG2kNCyxkF-LTw+Fm0WPpb-dzMfC4EStVSOEnyUtwKF7gPJP3g@mail.gmail.com" type="cite"> <div dir="ltr"> <div class="gmail_extra"> <div class="gmail_quote">On Thu, Feb 9, 2017 at 3:06 PM, <span dir="ltr"><<a moz-do-not-send="true" href="mailto:ovirt@timmi.org" target="_blank">ovirt@timmi.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi oVirt List,<br> <br> I'm trying to change the disk allocation policy of a VM disk and I'm not able to perform this task via the oVirt front-end.<br> <br> Is someone able to tell me how I can do that?<br> <br> Best regards and thank you<br> Christoph<br> <br> </blockquote> <div><br> </div> <div>I've done it in the past by creating a snapshot of a VM and then cloning the snapshot and selecting preallocated for the cloned disks (if you have to do it without powering off the source VM)</div> <div>Or directly creating a clone of the VM if it is powered off, I think it creates a full preallocated copy and btw you have no way to tell to clone as thin if I remember correctly</div> <div><br> </div> <div>Gianluca</div> </div> <br> </div> </div> </blockquote> <br> </body> </html> --------------6286BDE16222262E5DB9D903--
On Thu, Feb 9, 2017 at 4:11 PM, <ovirt@timmi.org> wrote:
Hi Gianluca,
I tried to clone the VM but it does not help. It is still thin allocation.
Best regards Christoph
Hi, I referred to this information for the clone of VM scenario: http://lists.ovirt.org/pipermail/users/2016-May/040129.html that contains: "
What happens if you clone a source VM which is using "thin" ? The VM cloned from a thin templated base VM will be created with a full copy of the disk (as in "Clone" when creating from template) " but I have not tried myself recently with 4.0/4.1 versions
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: VM is powered on create a snapshot of the VM select the snapshot line and select clone in resource allocation section of the new vm screen change allocation policy for the desired disk/s from thin provision to preallocated Then you can decommission old VM and use the cloned one Verified today in 4.1 too. Or from the snapshot line you can also "make template" if you plan to use it as a base for more VMs. 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). See my screenshot: https://drive.google.com/file/d/0BwoPbcrMv8mvTHIzTU5kdHVJOG8/view?usp=sharin... Probably it should be made consistent and show "Allocation Policy" instead and related values? Gianluca
On Thu, Feb 9, 2017 at 4:46 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Feb 9, 2017 at 4:11 PM, <ovirt@timmi.org> wrote:
Hi Gianluca,
I tried to clone the VM but it does not help. It is still thin allocation.
Best regards Christoph
Hi, I referred to this information for the clone of VM scenario: http://lists.ovirt.org/pipermail/users/2016-May/040129.html that contains:
"
What happens if you clone a source VM which is using "thin" ? The VM cloned from a thin templated base VM will be created with a full copy of the disk (as in "Clone" when creating from template) " but I have not tried myself recently with 4.0/4.1 versions
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: VM is powered on create a snapshot of the VM select the snapshot line and select clone in resource allocation section of the new vm screen change allocation policy for the desired disk/s from thin provision to preallocated Then you can decommission old VM and use the cloned one Verified today in 4.1 too.
Or from the snapshot line you can also "make template" if you plan to use it as a base for more VMs. 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). See my screenshot: https://drive.google.com/file/d/0BwoPbcrMv8mvTHIzTU5kdHVJOG8/ view?usp=sharing Probably it should be made consistent and show "Allocation Policy" instead and related values?
Gianluca
Hi, I just tested this on 4.1: - take a VM with a thin provisioned disk How to see allocation policy? It seems suboptimal for me: I would expect to see this kind of information in disks sub pane of the vm. 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 - make a clone of it in a new VM In the same sub pane for the new VM I see preallocated.... so it seems to work as I read This is on FC-SAN. What kind of storage is yours?
This is a multi-part message in MIME format. --------------C036F36AD63F1ED230FAAC1E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Gianluca, thank you for the feedback with the templates. I will take a look into it. Best regards Christoph Am 09.02.2017 um 21:12 schrieb Gianluca Cecchi:
On Thu, Feb 9, 2017 at 4:46 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@gmail.com>> wrote:
On Thu, Feb 9, 2017 at 4:11 PM, <ovirt@timmi.org <mailto:ovirt@timmi.org>> wrote:
Hi Gianluca,
I tried to clone the VM but it does not help. It is still thin allocation.
Best regards Christoph
Hi, I referred to this information for the clone of VM scenario: http://lists.ovirt.org/pipermail/users/2016-May/040129.html <http://lists.ovirt.org/pipermail/users/2016-May/040129.html> that contains:
" >What happens if you clone a source VM which is using "thin" ? The VM cloned from a thin templated base VM will be created with a full copy of the disk (as in "Clone" when creating from template) " but I have not tried myself recently with 4.0/4.1 versions
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: VM is powered on create a snapshot of the VM select the snapshot line and select clone in resource allocation section of the new vm screen change allocation policy for the desired disk/s from thin provision to preallocated Then you can decommission old VM and use the cloned one Verified today in 4.1 too.
Or from the snapshot line you can also "make template" if you plan to use it as a base for more VMs. 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). See my screenshot: https://drive.google.com/file/d/0BwoPbcrMv8mvTHIzTU5kdHVJOG8/view?usp=sharin... <https://drive.google.com/file/d/0BwoPbcrMv8mvTHIzTU5kdHVJOG8/view?usp=sharing> Probably it should be made consistent and show "Allocation Policy" instead and related values?
Gianluca
Hi, I just tested this on 4.1: - take a VM with a thin provisioned disk How to see allocation policy? It seems suboptimal for me: I would expect to see this kind of information in disks sub pane of the vm. 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
- make a clone of it in a new VM In the same sub pane for the new VM I see preallocated.... so it seems to work as I read This is on FC-SAN. What kind of storage is yours?
--------------C036F36AD63F1ED230FAAC1E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <span class="">Hi Gianluca,<br> <br> thank you for the feedback with the templates.<br> I will take a look into it.<br> <br> Best regards<br> Christoph<br> </span><br> <div class="moz-cite-prefix">Am 09.02.2017 um 21:12 schrieb Gianluca Cecchi:<br> </div> <blockquote cite="mid:CAG2kNCxBkjQkWAicysdKbhmB==Nx2zvWd9a-Q_OpdzFxBvdriQ@mail.gmail.com" type="cite"> <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 moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" href="https://drive.google.com/file/d/0BwoPbcrMv8mvTHIzTU5kdHVJOG8/view?usp=sharin..." 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> </blockquote> <br> </body> </html> --------------C036F36AD63F1ED230FAAC1E--
participants (2)
-
Gianluca Cecchi -
ovirt＠timmi.org