<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Hi!<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Regarding your examples, I cannot say exactly because of lack of some details. What storage type are you using? How do you measure the space used on the physical disk?<br><br>> For example, when making a VM from template, using pre-allocated disk
option, for a 50GB Virtual disk, it only uses 3GB on the physical disk.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">3GB is the VM's disk? What about the disk of the template?<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Generally, 50GB pre-allocated disk will take 50GB of physical space. A 50GB sparse disk will take as many 1GB chunks as needed to store all the information that was written to it, maximum 50GB.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">When you create a VM by cloning another VM or create a VM from a template in "clone" mode, a copy of the source disk will be created. The new disk will take as much space as the source disk did.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">When you create a VM from a template in "thin provision" mode or creating a VM in a pool, the new disk will be initially only a reference to the source disk. Reading from it will read the source disk. Writing to it will write to the new disk, not touching the source. Thus, all disk fragments that were overwritten after disk creation will be physically stored in the new disk and read from it, those that were not overwritten, will be read from the source disk.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Also note that pool VMs are stateless, so the information that was written to their disks when VM was used by user is erased after the VM is returned back to the pool.<br><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:x-small">Shmuel<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 23, 2016 at 12:50 PM, Alexis HAUSER <span dir="ltr"><<a href="mailto:alexis.hauser@telecom-bretagne.eu" target="_blank">alexis.hauser@telecom-bretagne.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
<br>
I would like to know what happens to storage when using the different method of cloning or generating VMs using templates / pools.<br>
I'd like to know also in what case VM and virtual disks are totally independent and in what case they are not.<br>
Sadly the RHEV documentation doesn't really provide these informations and I don't find any explicit informations about it.<br>
<br>
For example, when making a VM from template, using pre-allocated disk option, for a 50GB Virtual disk, it only uses 3GB on the physical disk.<br>
Another example, when making a pool of 10 VMs, based on a VM with a 50 GB virtual disk, only 2GB more space is used on the physical disk.<br>
What is exactly done when this happens ?<br>
<br>
Here are the case I would like to have informations about (physical storage, and independence of VMs) :<br>
- using simple "clone function"<br>
- making VM from template with "clone" mode<br>
- making VM from template with "thin" mode<br>
- making VM in pools<br>
<br>
Is there modes calculating only the difference from the original VM, and other modes copying totally the informations from the virtual disk from the original VM ?<br>
<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" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</blockquote></div><br></div>