3) About the attached logs the virtual machine made from template was finally made at: 2012/12/22 17:21 Logs are from 16:17 to 17:21 aproximately and I might reuse them to ask why it takes so long to make the virtual machine while checking the storage image at /home/storage (its size) it would seem that the > copy has finished. I think that the "Make vm from template" task started about 30 minutes or 40 minutes before it being finished. Well, that's the average time it takes for me. Since you are creating a server the default behaviour is to clone your disks, which means engine calls copyImage to the SPM. From what I saw in the logs your template have two disks, which one of
Hi Adrian, Sorry for the late respond. Please see inline comments, and feel free if there are any more questions, or other issues which you want us to address to. p.s. Since some of the responds were in different threads, I gathered all of them to this email. them is 1920 GB, this is why it took 30 minutes to copy it. If you want your copy to be faster, you can change the default in the resource allocation tab to use thin instead of clone when you add a new server. although, take in notice that when you will use thin provisioning, the server will be based on the template and you will not be able to remove the template until the VM will be removed. On 12/25/2012 09:34 PM, Adrian Gibanel wrote:> I've described the "Create template from VM" extending bug (the one I
was told in irc) but I've attached the "Create VM from template" logs.
If there's also a bug about "Create VM from template" being extended then it's useful. If it's not I'll try to recreate a "Create template from VM" task and attach the logs.
Sorry about the confusion. If you can still reproduce this scenario when you create a template with wrong provisioning, please attach the logs of it.
This is the right template disk allocation policy table (The fix is that second hard disk is preallocated instead of being Thin Prov)
Alias | Virtual Size | Allocation | Target First | 1920 GB | Thin Prov | local_storage Seco | 1 GB | Preallocat | local_storage I took a look in your logs, and it seems that when you create a VM from template the passing arguments are preallocated for one image and sparse for the other, so it seems that this is fit with the allocation policy
On 12/24/2012 01:51 AM, Adrian Gibanel wrote:> I've just noticed that I made a typo. table you sent.
----- Mensaje original -----
De: "Adrian Gibanel" <adrian.gibanel@btactic.com> Para: "users" <users@ovirt.org> Enviados: Lunes, 24 de Diciembre 2012 0:45:24 Asunto: Re: [Users] Thin provisioning extending while "Make template" still a bug?
1) So... the mentioned bug does exist or am I just experiencing a normal oVirt usage (Making a vm from template with thin provisioning works ok without extending)?
2) About template disk allocation policy...
When I create a new server based on template and I click on: Resource Allocation tab:
Template Provisioning: Clone
Alias | Virtual Size | Allocation | Target First | 1920 GB | Thin Prov | local_storage Seco | 1 GB | Thin Prov | local_storage
Regards, Maor