[PATCH container/qemu-server v3 0/2] api: clone: print a message with new VMID

[Maximiliano Sandoval <m.sandoval@proxmox.com>]

Note that when creating linked clones we do not update the creation time (commits)
in the config.

When cloning two VMs from a template (created with "vanilla" settings),
if one uses the same 'name' for both clones, then the only differences
between the linked clones that could be used to tell them apart are the
MAC address, the VM id, smbios UUID, and the vmgenid, all of which are
randomly generated.

I think it makes sense to update the creation time too. But for now,
being able to tell from the task log which VM correspond to which
qmclone task would be an improvement already.

Tested:
 - create a template with id 101
 - running: qm clone 101 206 --full 0, and checking its output
   creating a clone of 101 with ID 206
   create linked clone of drive scsi0 (local-lvm:base-101-disk-0)

Differences from v2:
 - s/creating a clone of $vmid/creating a clone of VM $vmi
 - Add a similar line to pve-container's clone 

Differences from v1:
 - Moved the message to the start of $clonefn


qemu-server:

Maximiliano Sandoval (1):
  api: qmclone: print a message with new VMID

 src/PVE/API2/Qemu.pm | 3 +++
 1 file changed, 3 insertions(+)


pve-container:

Maximiliano Sandoval (1):
  api: vm_clone: print a message with new VMID

 src/PVE/API2/LXC.pm | 2 ++
 1 file changed, 2 insertions(+)


Summary over all repositories:
  2 files changed, 5 insertions(+), 0 deletions(-)

-- 
Generated by murpp 0.10.0