VM to Template Conversion

[gfngfn256]

TLDR: "Convert to template" should become "Create template"


I know this is a request feature of sorts - I hope its OK to post it here.

I know that when you convert a VM to a Template, the VM is no longer runnable, since the VM itself has been converted to a Template & no longer exists.

So in fact, the workable way, if you still want the VM after converting to Template, is to first Fully Clone the VM & then convert the clone to a Template.

However, countless times, (tiredness & forgetfulness), I just go ahead & convert to template, bingo & I've lost the VM. I then have to either go ahead & recreate from backup, or create a new full clone from the Template, and start again.

Everybody knows, often/usually a Template has to be further tested/tweaked & if you've lost the original VM - well you have to start again.

Looking on this forum & many other web sites - you'll see how many users learn this - the hard way.

Yes, the documentation states this in a small Note - but this obviously isn't enough for many.


I believe, that the default action for creating a Template from a VM, should be that the system first fully clones the VM & then converts that clone to a VM.

I realize some may find the removal of the original VM practical - I believe the majority of users will disagree.

 

[bbgeek17]

since the VM itself has been converted to a Template & no longer exists.

Technically the VM still exists, the disk is renamed from vm-id-disk-id to vm-id-base and a flag is added to config file. You can revert back to VM in-place if you really wanted to.

first Fully Clone the VM & then convert the clone to a Template.

create a new full clone from the Template

Aren't these two equivalent?

Template has to be further tested/tweaked & if you've lost the original VM - well you have to start again.

You should probably incorporate snapshots into your workflow. Rolling back seems much more efficient than starting again.

I believe, that the default action for creating a Template from a VM, should be that the system first fully clones the VM & then converts that clone to a VM.

The current behavior has been in place for a decade or so. There are multiple existing production workflows that rely on this. PVE developers are rightfully conservative about changing existing behavior, so I don't see that default will be changed under any circumstances. But especially when driven by "tiredness & forgetfulness".

I know this is a request feature of sorts - I hope its OK to post it here.

You can put it here, but it has very low chance of being picked up or looked at by staff. bugzilla is the right place for bugs or enhancement requests.

good luck.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox