I am really confused. Please can someone help me understand what's happening?
When I delete a VM Template from which I created a linked clone, the linked clone continues to work perfectly.
This is not what I expected and I have obviously misunderstood something. From what I've read, I thought a linked clone only created a "blank" filesystem, where additions/changes to the source VM would be stored. So if you destroy the source Template, the linked clone should stop working. But in my case it continues to work.
Please can someone clear up my misunderstanding? I feel very stupid asking this question. I would prefer to post in the "Newbie Stupid Question" section of the forum, but it seems not to exist.....
In case it is useful, this is what I did (Proxmox 5.2-5):
I created a Centos 7 VM (ID=101), then converted it into a Template.
In local-lvm, I can see base-101-disk-1 which is the disk image for this template (format = raw, type = disk image, size=32GB, this being the size I specified when creating the VM before turning it into a Template)
I then create a new linked clone (VM ID=103) from the Template . It takes 2 seconds, so it is definitely a linked clone not a full clone, which takes a much, much longer time.
in local-lvm, I can see vm-103-disk-1 (format = raw, type = disk image, size=32GB).
lvdisplay shows " LV Thin origin name base-101-disk-1" for /dev/pve/vm-103-disk1
So far so good.
Now if I Remove the Template (ID=101), it vanishes from the GUI, and base-101-disk-1 vanishes from local-lvm.
But somehow VM 103 still works fine.
In addition, lvdisplay now has no "LV Thin origin name" line for /dev/pve/vm-103-disk1
When I delete a VM Template from which I created a linked clone, the linked clone continues to work perfectly.
This is not what I expected and I have obviously misunderstood something. From what I've read, I thought a linked clone only created a "blank" filesystem, where additions/changes to the source VM would be stored. So if you destroy the source Template, the linked clone should stop working. But in my case it continues to work.
Please can someone clear up my misunderstanding? I feel very stupid asking this question. I would prefer to post in the "Newbie Stupid Question" section of the forum, but it seems not to exist.....
In case it is useful, this is what I did (Proxmox 5.2-5):
I created a Centos 7 VM (ID=101), then converted it into a Template.
In local-lvm, I can see base-101-disk-1 which is the disk image for this template (format = raw, type = disk image, size=32GB, this being the size I specified when creating the VM before turning it into a Template)
I then create a new linked clone (VM ID=103) from the Template . It takes 2 seconds, so it is definitely a linked clone not a full clone, which takes a much, much longer time.
in local-lvm, I can see vm-103-disk-1 (format = raw, type = disk image, size=32GB).
lvdisplay shows " LV Thin origin name base-101-disk-1" for /dev/pve/vm-103-disk1
So far so good.
Now if I Remove the Template (ID=101), it vanishes from the GUI, and base-101-disk-1 vanishes from local-lvm.
But somehow VM 103 still works fine.
In addition, lvdisplay now has no "LV Thin origin name" line for /dev/pve/vm-103-disk1