VM shuts down for no apparent reason

[rpereyra]

Hello

I have a fairly old installation of proxmox 6.4.13 where something is happening that has never happened before.

The server has been working fine for years, but a few days ago a virtual machine has been shutting down in the early hours of the morning. I start it from the dashboard and it starts fine.

The only record I find in the node is this one in:

/var/log/syslog

May 17 04:48:26 pm4 systemd[1]: 100.scope: Succeeded.
May 17 04:48:27 pm4 qmeventd[3459]: Starting cleanup for 100
May 17 04:48:27 pm4 qmeventd[3459]: Finished cleanup for 100

When this happens the server shuts down with no apparent reason.
That could be happening

Thank you all very much in advance

Roberto

 

[rpereyra]

I add that there are 10 vms on this server and it is the only one that is turned off

roberto

 

[fiona]

Hi,
please share more of the surrounding log. Is there any task that is running around that time, e.g. backup? It might be that the guest inside the VM shuts down, please also check the logs there.

Please note that Proxmox VE 6.x has been end-of-life since more than 1.5 years now:
https://pve.proxmox.com/wiki/FAQ
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8

 

[rpereyra]

Yes, a backup is running on it, which has been running for years without problems, by the time VM 100 is turned off its backup has finished.

The backup continues with the other VMs without problems.

---------------------
INFO: starting new backup job: vzdump 100 101 102 103 105 106 --quiet 1 --mode snapshot --compress lzo --storage pm4 --mailnotification always
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2024-05-17 02:00:02
INFO: status = running
INFO: VM Name: produccion1.gchu.ar
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 300G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/pm4/dump/vzdump-qemu-100-2024_05_17-02_00_02.vma.lzo'
INFO: started backup task '881dcac1-6f04-4f31-b8f3-192fcff80ffa'
INFO: resuming VM again
INFO: 0% (543.8 MiB of 300.0 GiB) in 3s, read: 181.3 MiB/s, write: 126.5 MiB/s
INFO: 1% (3.1 GiB of 300.0 GiB) in 40s, read: 69.8 MiB/s, write: 67.1 MiB/s
...............
INFO: 96% (288.0 GiB of 300.0 GiB) in 1h 2m 26s, read: 58.1 MiB/s, write: 57.4 MiB/s
INFO: 97% (291.1 GiB of 300.0 GiB) in 1h 3m, read: 91.9 MiB/s, write: 89.4 MiB/s
INFO: 98% (294.1 GiB of 300.0 GiB) in 1h 3m 49s, read: 63.4 MiB/s, write: 62.6 MiB/s
INFO: 99% (297.1 GiB of 300.0 GiB) in 1h 4m 23s, read: 90.0 MiB/s, write: 87.9 MiB/s
INFO: 100% (300.0 GiB of 300.0 GiB) in 1h 5m 3s, read: 74.8 MiB/s, write: 74.0 MiB/s
INFO: backup is sparse: 5.03 GiB (1%) total zero data
INFO: transferred 300.00 GiB in 3903 seconds (78.7 MiB/s)
INFO: archive file size: 192.50GB
INFO: removing backup 'pm4:backup/vzdump-qemu-100-2024_05_15-02_00_01.vma.lzo'
INFO: Finished Backup of VM 100 (01:05:18)
INFO: Backup finished at 2024-05-17 03:05:20
----------------------

Thanks for any help

roberto

 

[fiona]

Is the guest maybe in S3 sleep/suspend state at the time the backup ends?
There is a rather recent fix for such cases in qemu-server >= 8.2.0 https://git.proxmox.com/?p=qemu-server.git;a=commit;h=81a8c4e5ee44af91dc283bc5ebf4760f0b8b8a51

 

[rpereyra]

I'm going to see what condition it's in when it happens again.
Thank you very much for that info.

When I have more data I will update the thread.

Thanks a lot

Roberto