Hi,

one question - what I have noticed, need confirmation please.

I have made one volume templates (50GB) (win2008, sysreped, etc).

When I deployed 1 VM from that template, it created 1 clone of the original
template volume of 50GB, and it is declared as backing file

When i deployed another VM from that template, I can see that this VM now
have "differential" disk, that is a disk that has it's backing disk.

[root@cs2 ~]# qemu-img info
/var/lib/libvirt/images/87924eb1-1e46-4e93-8735-7cff0daefd40
image: /var/lib/libvirt/images/87924eb1-1e46-4e93-8735-7cff0daefd40
file format: qcow2
virtual size: 50G (53687091200 bytes)
*disk size: 177M*
cluster_size: 65536
backing file: /var/lib/libvirt/images/*65e6c5a8-0c60-41e9-ba2f-9f1c82282d1a*

[root@cs2 ~]# qemu-img info /var/lib/libvirt/images/*
65e6c5a8-0c60-41e9-ba2f-9f1c82282d1a*
image: /var/lib/libvirt/images/65e6c5a8-0c60-41e9-ba2f-9f1c82282d1a
file format: qcow2
virtual size: 50G (53687091200 bytes)
disk size: 12G
cluster_size: 65536

Is this the default behaviour when deploying new VM from template - first
create clone of the original template volume in full size (50Gb), and then
create differentials disks for each VM, refering to this one main
volume(backing disk) ?

Thanks,


-- 

Andrija Panić

Reply via email to