You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Andrija Panic <an...@gmail.com> on 2013/10/28 17:00:35 UTC
CS 4.2 make backing file when deployed from snapshot
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ć
Re: CS 4.2 make backing file when deployed from snapshot
Posted by Andrija Panic <an...@gmail.com>.
Thanks, that's what I thought..
Best,
Andrija
On 28 October 2013 18:03, Geoff Higginbottom <
geoff.higginbottom@shapeblue.com> wrote:
> Hi Andrija,
>
> The use of Linked Clones is the default behaviour. It allows for quick
> deployment of VMs and very efficient use of storage.
>
> If you were using VMware you can now change the behaviour to not use
> Linked Clones.
>
> Regards
>
> Geoff Higginbottom
>
> D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
>
> geoff.higginbottom@shapeblue.com
>
> -----Original Message-----
> From: Andrija Panic [mailto:andrija.panic@gmail.com]
> Sent: 28 October 2013 16:01
> To: users@cloudstack.apache.org
> Subject: CS 4.2 make backing file when deployed from snapshot
>
> 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ć
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue is a
> registered trademark.
>
--
Andrija Panić
RE: CS 4.2 make backing file when deployed from snapshot
Posted by Geoff Higginbottom <ge...@shapeblue.com>.
Hi Andrija,
The use of Linked Clones is the default behaviour. It allows for quick deployment of VMs and very efficient use of storage.
If you were using VMware you can now change the behaviour to not use Linked Clones.
Regards
Geoff Higginbottom
D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581
geoff.higginbottom@shapeblue.com
-----Original Message-----
From: Andrija Panic [mailto:andrija.panic@gmail.com]
Sent: 28 October 2013 16:01
To: users@cloudstack.apache.org
Subject: CS 4.2 make backing file when deployed from snapshot
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ć
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.