Hello,
today I wanted to create a vm snapshot. The storage backend is a own ceph cluster so its not hyperconverged.
I forgot to deactivate the RAM snapshot option and started, it slowly proceeded the VMs RAM and so I decided to cancel the snapshot.
Afterwards I had a locked VM with am
This helped as in the interface the snapshot was no longer displayed. On the ceph side I manuall deleted the
Well my pleasure about this success was to quick: I tried to create a new snapshot for the very same VM, this time without RAM but the system told me:
Now I am unsure how to get rid of this error. Does it help to shut the VM down (cannot try before the evening)? Any other ideas?
Tahnks
Rainer
today I wanted to create a vm snapshot. The storage backend is a own ceph cluster so its not hyperconverged.
I forgot to deactivate the RAM snapshot option and started, it slowly proceeded the VMs RAM and so I decided to cancel the snapshot.
Afterwards I had a locked VM with am
vm-<id>-state-<snapname>
on the cephside created. I was able to unlock the vm using qm unlock
. But still I was unable to delete the snapshot in the proxmox interface so I searched in the forum and found the hint to run qm delsnapshot id snapname --force
This helped as in the interface the snapshot was no longer displayed. On the ceph side I manuall deleted the
vm-<id>-state-<snapname>
rbd image.Well my pleasure about this success was to quick: I tried to create a new snapshot for the very same VM, this time without RAM but the system told me:
snapshot create failed: starting cleanup
TASK ERROR: VM 116 qmp command 'savevm-start' failed - VM snapshot already started
Now I am unsure how to get rid of this error. Does it help to shut the VM down (cannot try before the evening)? Any other ideas?
Tahnks
Rainer