Guest powered off after snapshot backup

Valerio Pachera

Active Member
Aug 19, 2016
131
7
38
43
The 13th March 23:30 proxmox started doing vm backup.
This morning I found the the guest id 100 powered off.
I noticed the message 'VM is locked'.

upload_2018-3-14_9-55-25.png

In /var/log/messages I see

Code:
grep ' qm' /var/log/messages
Mar 12 23:10:01 cavaion-proxmox-ve qm[25074]: <root@pam> starting task UPID:cavaion-proxmox-ve:000061F3:02E2D531:5AA6FAB9:qmshutdown:100:root@pam:
Mar 12 23:10:08 cavaion-proxmox-ve qm[25074]: <root@pam> end task UPID:cavaion-proxmox-ve:000061F3:02E2D531:5AA6FAB9:qmshutdown:100:root@pam: OK
Mar 13 00:24:01 cavaion-proxmox-ve qm[30475]: <root@pam> starting task UPID:cavaion-proxmox-ve:0000770C:02E99B82:5AA70C11:qmstart:100:root@pam:
Mar 13 00:24:04 cavaion-proxmox-ve qm[30475]: <root@pam> end task UPID:cavaion-proxmox-ve:0000770C:02E99B82:5AA70C11:qmstart:100:root@pam: OK
Mar 13 23:10:01 cavaion-proxmox-ve qm[134244]: <root@pam> starting task UPID:cavaion-proxmox-ve:00020C65:0366AB2F:5AA84C39:qmshutdown:100:root@pam:
Mar 13 23:10:07 cavaion-proxmox-ve qm[134244]: <root@pam> end task UPID:cavaion-proxmox-ve:00020C65:0366AB2F:5AA84C39:qmshutdown:100:root@pam: OK
Mar 13 23:30:03 cavaion-proxmox-ve qm[135736]: <root@pam> update VM 100: -lock backup
Mar 14 00:25:56 cavaion-proxmox-ve qm[139868]: <root@pam> starting task UPID:cavaion-proxmox-ve:0002225D:036D9E24:5AA85E04:qmstart:100:root@pam:
Mar 14 03:52:20 cavaion-proxmox-ve qm[154985]: <root@pam> update VM 102: -lock backup
Mar 14 05:13:45 cavaion-proxmox-ve qm[160901]: <root@pam> update VM 103: -lock backup
Mar 14 05:21:32 cavaion-proxmox-ve qm[161456]: <root@pam> update VM 106: -lock backup
Mar 14 06:01:51 cavaion-proxmox-ve qm[164374]: <root@pam> update VM 107: -lock backup

Any idea of whant may have caused this issue?

Proxmox VE 4.4-1/eb2d6f1e

upload_2018-3-14_9-58-32.png
 
Hi,

Please update to the current version, your version is over 2 Years old.
 
Right now, I can't update that server.
I tried to backup a single guest each day and only a one guest is giving the lock problem (a windows 2012).
Note: this is the only windows guest with qemu-ga.
Because this is a production server, I can't do much testing.
Do you think the issue may be related to qemu-ga?
Or is there any log I can check to get more info?

Thank you.
 
Do you think the issue may be related to qemu-ga?
No qga will skipped if do not work proper.
I think it is an windows driver problem.
Can you send the VM config of this VM?
 
Here it is:

Code:
agent: 1
balloon: 2048
boot: c
bootdisk: scsi0
cores: 8
cpu: host
ide2: local:iso/virtio-win.iso,media=cdrom,size=152204K
keyboard: it
localtime: 1
memory: 24576
name: win2012
net0: e1000=0E:4C:07:AF:81:06,bridge=vmbr0
numa: 1
onboot: 1
ostype: win8
scsi0: big:vm-100-disk-1,cache=writeback,discard=on,size=200G
scsi1: big:vm-100-disk-3,cache=writeback,discard=on,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=1270bf4b-1e1c-4df3-918a-a2414488e156
sockets: 1
startup: order=2