Resume from hibernate failed: got timeout. How to increase 300sec timeout?

Vasily Poterjyko

Renowned Member
Aug 1, 2011
19
2
68
Restoring a heavy machine with >270Gb RAM. The state of the machine is on SSD disks, reading the entire volume of this file takes less than 300 seconds, but I still get the timeout of the machine restore operation from hibernate.
How to increase VM recovery timeout?
I also want to note that saving the state of the virtual machine to disk took more than 11 minutes.

https://paste.ofcode.org/38KgvzZYjvexytd6JZLiAtY

Code:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-7
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-6
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1
 
there is sadly no mechanism currently to manually increase the timeout, but
you could temporarily edit the file in '/usr/share/perl5/PVE/QemuServer/Helpers.pm' to increase the $timeout = 300; to e.g. 600
(note that you must restart the pveproxy and pvedaemon after editing that file, and this change will be overwritten on the next update)

you can open a bug report for configuring a manual timeout: https://bugzilla.proxmox.com
 
  • Like
Reactions: Vasily Poterjyko
Increasing the timeout in Helpers.pm did not help me upon first try. I did not dig deeper. However, I was able to see the /usr/bin/kvm command in the "Task Viewer" window when I double clicked on the "VM 129 -- Resume" line in the task log. Running this from the command line then ran to completion succesfully.
 
  • Like
Reactions: fpdragon
Thanks a lot.

This has worked for me.

1.) Copy the /usr/bin/kvm command from the failed log entry.
2.) Open a shell and execute the command.
3.) Wait very long. You should see the rising RAM usage.
4.) If the command has finished the VM should run again.
But the UI still shows a different icon.
5.) Remove the Hibernation VM State image file from the "Hardware" section of the VM. This should fix the GUI inidicators and buttons.
 

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!