Hi all,
I am encountering a persistent issue when trying to take a live snapshot (with RAM included) of a specific VM. The task fails initially, and subsequent attempts get blocked by a locked snapshot state.
Here is the error log from the first snapshot attempt:
When I try to run the snapshot task again immediately after the failure, it consistently rejects the command with the following error:
Full log in attachments.
I have attached the detailed log files regarding this issue to this post for reference.
Here is the pveversion -v output of the node:
Here is the configuration file of the target VM:
I am encountering a persistent issue when trying to take a live snapshot (with RAM included) of a specific VM. The task fails initially, and subsequent attempts get blocked by a locked snapshot state.
Here is the error log from the first snapshot attempt:
Bash:
snapshot create failed: starting cleanup
TASK ERROR: unable to save VM state and RAM - qemu_savevm_state_complete_precopy error -5When I try to run the snapshot task again immediately after the failure, it consistently rejects the command with the following error:
Bash:
snapshot create failed: starting cleanup
TASK ERROR: VM 12203 qmp command 'savevm-start' failed - VM snapshot already startedFull log in attachments.
I have attached the detailed log files regarding this issue to this post for reference.
Here is the pveversion -v output of the node:
Bash:
proxmox-ve: 9.1.0 (running kernel: 7.0.0-3-pve)
pve-manager: 9.1.9 (running version: 9.1.9/ee7bad0a3d1546c9)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-7.0: 7.0.0-3
proxmox-kernel-7.0.0-3-pve-signed: 7.0.0-3
proxmox-kernel-6.17: 6.17.13-6
proxmox-kernel-6.17.13-6-pve-signed: 6.17.13-6
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
amd64-microcode: 3.20250311.1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.10-pve2
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx12
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.1
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.7
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.1.2
libpve-cluster-perl: 9.1.2
libpve-common-perl: 9.1.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.3.0
libpve-notify-perl: 9.1.2
libpve-rs-perl: 0.13.0
libpve-storage-perl: 9.1.2
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-4
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-4
proxmox-backup-client: 4.2.0-1
proxmox-backup-file-restore: 4.2.0-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.3
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.9
pve-cluster: 9.1.2
pve-container: 6.1.5
pve-docs: 9.1.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-3
pve-ha-manager: 5.2.0
pve-i18n: 3.7.1
pve-qemu-kvm: 10.1.2-7
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.9
smartmontools: 7.4-pve1
spiceterm: 3.4.2
swtpm: 0.8.0+pve3
vncterm: 1.9.2
zfsutils-linux: 2.3.4-pve1Here is the configuration file of the target VM:
Bash:
agent: 1
boot: order=virtio0
cipassword:
ciupgrade: 0
ciuser: root
cores: 15
cpu: host
cpulimit: 15
ide0: none,media=cdrom
ipconfig0: ip=103.9.24.15/24,gw=103.9.24.1
kvm: 1
lock: backup
memory: 47104
name: vina
nameserver: 8.8.8.8
net0: virtio=BC:24:11:94:24:54,bridge=vmbr0,firewall=1,queues=4,rate=51,tag=200
numa: 1
onboot: 1
ostype: other
scsihw: lsi
searchdomain: viet.vn
serial0: socket
smbios1: uuid=b509e2e9-56c5-43b8-bb0b-e86136cecf57
sockets: 1
tags:
vga: std
virtio0: vms:vm-12203-disk-0,cache=directsync,discard=on,format=raw,iops_rd=95000,iops_wr=35000,iothread=1,size=400G
vmgenid: 435982d1-0cc1-4601-98e6-d5251e277be7
