Can't remove VM after cloning

[cdsJerry]

I had a VM which I wanted to rename. I did a search of the forum and it said the way to do that was to clone the VM and use the new name in the clone so I did that.

So now I'd like to delete the original VM with the old name however the Remove option is dimmed from the menu so I can't delete it. I can delete the clone, but not the original VM.

I also noticed that the clone icon is different than the other icons. It's grayer than the other VMs. The original VM is also not as dark as the other VMs. I'm sure the color differences are a way of letting me know there's a clone out there and that's clever. However, how do I kill the original so I'm only left with the Clone (new)?

I'm running Proxmox VE 6.1-3

 

[mplssilva]

good morning,
check the proxmox task log, if cloning completed success.

in console of your Proxmox, unlock VM:
qm unlock VM-ID-Number

 

[cdsJerry]

Tricky. On the summary screen it shows the status as "OK " after cloning. However when I look at the log I see this:

drive-virtio0: transferred: 751512322048 bytes remaining: 106954752 bytes total: 751619276800 bytes progression: 99.99 % busy: 1 ready: 0
drive-virtio0: transferred: 751529099264 bytes remaining: 90177536 bytes total: 751619276800 bytes progression: 99.99 % busy: 1 ready: 0
drive-virtio0: transferred: 751619276800 bytes remaining: 0 bytes total: 751619276800 bytes progression: 100.00 % busy: 1 ready: 0
drive-virtio0: transferred: 751619276800 bytes remaining: 0 bytes total: 751619276800 bytes progression: 100.00 % busy: 0 ready: 1
all mirroring jobs are ready
Qemu Guest Agent is not running - VM 103 qmp command 'guest-ping' failed - got timeout
suspend vm
trying to acquire lock...
drive-virtio0: Cancelling block job
drive-virtio0: Done.
resume vm
trying to acquire lock...

So it looks like it failed after all but after reaching 100%?????

It took forever to clone this thing in the first place. It's a 700GB VM and I had the source and target both on the same local RAID 10 drive. I never thought it would take so long.

So it looks like it failed after 100% so I need to do it again.

 

[mplssilva]

try to verify sufficient disk space / disk partitions in Proxmox.

 

[cdsJerry]

Yes, plenty of space. The drive is only 20% used at this point.