Can no longer delete snapshots from one vm.

[binaryjay]

Every time I create a snapshot for a particular VM, and then try to delete it... the deletion dialog goes on forever never completing. If I cancel it, the VM gets stuck in a locked state. I can manually unlock it using qm unlock, and then edit the conf file to remove the snapshot section and everything appears to be fine again but if I create a new snapshot and then try to delete it, the cycle repeats.

Any advice on what I'm forgetting to "clear out" here, so I can get this thing back to a sane state again would be appreciated.

 

[Dunuin]

Might help if you tell us what storage is underneath. PVE knows several kinds of snapshots. Qcow2, ZFS, LVM, ... all got their own snapshot implementations.
Is there anything in the syslog?
Whats the config file of your guest you try to snapshot?

 

[binaryjay]

This one is QCOW2.

Oct 21 08:17:40 BinaryProx pvestatd[918]: VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 31 retries Oct 21 08:17:40 BinaryProx pvestatd[918]: status update time (6.467 seconds) Oct 21 08:19:05 BinaryProx pvedaemon[236229]: <root@pam> starting task UPID:BinaryProx:00039BE7:00778E1A:63528E39:qmdelsnapshot:100:root@pam: Oct 21 08:19:05 BinaryProx pvedaemon[236519]: <root@pam> delete snapshot VM 100: BeforeUpgrade Oct 21 08:19:05 BinaryProx pvedaemon[236519]: VM is locked (snapshot-delete) Oct 21 08:19:05 BinaryProx pvedaemon[236229]: <root@pam> end task UPID:BinaryProx:00039BE7:00778E1A:63528E39:qmdelsnapshot:100:root@pam: VM is locked (snapshot-delete)

agent: 1 balloon: 2048 bootdisk: scsi0 cores: 4 cpu: host memory: 7680 name: binaryserver net0: virtio=1A:B3:D9:16:65:91,bridge=vmbr0,firewall=1 numa: 0 onboot: 1 ostype: l26 parent: BeforeUpgrade scsi0: images:100/vm-100-disk-0.qcow2,discard=on,size=96G,ssd=1 scsihw: virtio-scsi-pci smbios1: uuid=7883b3e6-328a-4ea0-bf26-cdd98701ece3 sockets: 1 vmgenid: 905a0d39-815d-4428-9a29-fb55ca91b6b7

By the way this used to work fine on this VM until now. Both the VM and Proxmox has been restarted which did not seem to change anything.