Hi all,
tried to restore a backup of a VM created by the scheduled mechanism. The configuration of the backup job looks like
After the restore I got an additional entry in the list of hardware called "Hibernation VM State local-zfs:vm-501-state-suspend-2024-07-05"
So far so good ... but when I want to start the VM I get
"pveversion" says
pve-manager/8.2.4/faa83925c9641325 (running kernel: 6.8.12-1-pve)
which might be a newer version than the one the backup was created with.
After deleting the hibernation entry in the hardware list I'm able to start the VM but of course that's not the inteded behavior I assume. I found no information here that addresses my topic. It happens on my home lab environment which is kind of a prototype for a productive setup. Any hints would be appreciated to explain what's going on here.
That "vmstate:" entry is only in that backup for this VM. All other backups are done without that suspend file despite all of them are configured to make the backup as "snapshot".
tried to restore a backup of a VM created by the scheduled mechanism. The configuration of the backup job looks like
Code:
#<div align='center'><a href='https://Helper-Scripts.com' target='_blank' rel='noopener noreferrer'><img src='https://raw.githubusercontent.com/tteck/Proxmox/main/misc/images/logo-81x112.png'/></a>## # Home Assistant OS## <a href='https://ko-fi.com/D1D7EP4GF'><img src='https://img.shields.io/badge/☕-Buy me a coffee-blue' /></a># </div>
agent: 1
bios: ovmf
boot: order=scsi0
cores: 2
cpu: host
cpulimit: 2
efidisk0: local-zfs:vm-501-disk-0,efitype=4m,size=1M
localtime: 1
memory: 6144
meta: creation-qemu=8.1.2,ctime=1706283864
name: HomeAssistant
net0: virtio=02:2A:1B:96:96:E9,bridge=vmbr1,tag=61
net1: virtio=BC:24:11:BF:95:43,bridge=vmbr1,tag=88
numa: 0
onboot: 1
ostype: l26running
cpu: host,+kvm_pv_eoi,+kvm_pv_unhalt
runningmachine: pc-i440fx-9.0+pve0
scsi0: local-zfs:vm-501-disk-1,cache=writethrough,discard=on,iothread=1,size=32G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=38755c7c-1dbb-4553-94b4-ad50c93f392d
sockets: 1
startup: order=7,up=60,down=60
tablet: 0
tags: services
vmgenid: 2c35b8a8-9c9d-42d2-9b79-9dbdc4929100
vmstate: local-zfs:vm-501-state-suspend-2024-07-05
#qmdump#map:efidisk0:drive-efidisk0:local-zfs:raw:
#qmdump#map:scsi0:drive-scsi0:local-zfs:raw:After the restore I got an additional entry in the list of hardware called "Hibernation VM State local-zfs:vm-501-state-suspend-2024-07-05"
So far so good ... but when I want to start the VM I get
Code:
Resuming suspended VM
activating and using 'local-zfs:vm-501-state-suspend-2024-07-05' as vmstate
TASK ERROR: timeout: no zvol device link for 'vm-501-state-suspend-2024-07-05' found after 300 sec."pveversion" says
pve-manager/8.2.4/faa83925c9641325 (running kernel: 6.8.12-1-pve)
which might be a newer version than the one the backup was created with.
After deleting the hibernation entry in the hardware list I'm able to start the VM but of course that's not the inteded behavior I assume. I found no information here that addresses my topic. It happens on my home lab environment which is kind of a prototype for a productive setup. Any hints would be appreciated to explain what's going on here.
That "vmstate:" entry is only in that backup for this VM. All other backups are done without that suspend file despite all of them are configured to make the backup as "snapshot".
Last edited: