Snapshot 2TB larger disk

LLevon

New Member
Jun 7, 2023
5
0
1
When I try to take a snapshot with a larger disk of 2tb it takes a long time hangs and does not take the snapshot and this message appears

VM 175 qmp command 'savevm-end' failed - unable to connect to VM 175 qmp socket - timeout after 5985 retries
snapshot create failed: starting cleanup
TASK ERROR: VM 175 qmp command 'blockdev-snapshot-internal-sync' failed - got timeout
 
Hi,
what kind of underlying storage do you have? The timeout is currently 10 minutes. The fact that the VM will be blocked during the time it takes to snapshot the disk can't be easily changed.
 
Hi,
what kind of underlying storage do you have? The timeout is currently 10 minutes. The fact that the VM will be blocked during the time it takes to snapshot the disk can't be easily changed.
Hi,

My type of disc is VirtIO Block, My data is fictitious as test occupying 2tb
 
My type of disc is VirtIO Block, My data is fictitious as test occupying 2tb
But where is the disk located? Is it a qcow2 disk on a network share, a local raw file, ZFS volume, or something else?
 
Is it actual fake data or is the disk mostly empty? Can you share the output of qm config <ID> --current and of pveversion -v? While the VM is down, how log does running
Code:
time qemu-img snapshot -c newsnap /path/to/your/image/vm-<ID>-disk-<N>.qcow2
take?
You can remove the snapshot again with
Code:
qemu-img snapshot -d newsnap /path/to/your/image/vm-<ID>-disk-<N>.qcow2
.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!