Problems with backup (stop mode)

[durbano]

Hello everyone,
I've been having problems making my scheduled backups for a while now.
These are configured in STOP mode. I have verified that, when the copy starts, the machine shutdown order is sent, but it does not turn off, but instead restarts.

Sometimes the copies are made and other times I always get the same error: "command 'qm shutdown 101 --skiplock --keepActive --timeout 600' failed: exit code 255"

Detailed backup logs:
vzdump 101 --mailnotification always --quiet 1 --storage vm_storage_3 --mode stop --compress zstd --mailto xxxx@xxxx.com

101: 2023-07-10 23:00:02 INFO: Starting Backup of VM 101 (qemu)
101: 2023-07-10 23:00:02 INFO: status = running
101: 2023-07-10 23:00:02 INFO: backup mode: stop
101: 2023-07-10 23:00:02 INFO: ionice priority: 7
101: 2023-07-10 23:00:02 INFO: VM Name: XXXXX
101: 2023-07-10 23:00:05 INFO: include disk 'sata0' 'vm_storage_1:101/vm-101-disk-0.qcow2' 200G
101: 2023-07-10 23:00:06 INFO: stopping virtual guest
101: 2023-07-10 23:00:09 INFO: VM 101 qmp command 'query-status' failed - unable to connect to VM 101 qmp socket - timeout after 31 retries
101: 2023-07-10 23:10:09 INFO: VM quit/powerdown failed
101: 2023-07-10 23:10:09 ERROR: Backup of VM 101 failed - command 'qm shutdown 101 --skiplock --keepActive --timeout 600' failed: exit code 255

I have the agent install in the VM (Windows 10 Pro).

Below I show you the configuration of my machine (100.conf):

agent: 1
boot: order=scsi0;net0;ide0
cores: 2
ide0: none,media=cdrom
machine: pc-i440fx-7.2
memory: 16384
meta: creation-qemu=7.2.0,ctime=1693895517
name: MODULA
net0: virtio=BA:19:21:18:7E:BC,bridge=vmbr0,firewall=1
net1: virtio=CA:55:31C:79:15,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
scsi0: vm_storage_1:100/vm-100-disk-0.qcow2,cache=writeback,discard=on,size=200G
scsihw: virtio-scsi-pci
smbios1: uuid=3238d25b-5889-4e60-b3eb-1b9b20f9040c
sockets: 2
vmgenid: 622f35ec-96e3-46ac-9bec-d4d8e12a1749

Can you help me solve my problem?
Thanks in advance.

 

[hd--]

Hello
is it possible to manually shutdown and restart the VM ?
And have you checked if the guestagent is running correct ? qm agent <vmid> ping

 

[durbano]

Hi, thanks for your replay.
I can shutdown the vm manually without problems. The agent works perfectly.

 

[hd--]

Okay that is strange.
Is your Host fully updated, can you send the ourput of pveversion -v
And can you also check if there are some applications running which could block the shutdown(Can't be stopped) in the windowsVM ?

 

[durbano]

Hi,

root@pve:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.126-1-pve)
pve-manager: 7.4-17 (running version: 7.4-17/513c62be)
pve-kernel-5.15: 7.4-7
pve-kernel-5.15.126-1-pve: 5.15.126-1
pve-kernel-5.15.116-1-pve: 5.15.116-1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-5
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

As far as I know, I don't have any application that is blocking me from shutting down Windows gracefully.

thanks for your help!

 

[hd--]

You could try to deactivate the qemu-guest-agent and check if the automated shutdown is working then, as the shutdown is then executed via ACPI (which is normally not the preferred way of doing it)
If not activate the qemu-guest-agent again and update the qemu-guest-agent in your windows VM.

Also your host is still running PVE 7.4 and you could think about updating to 8.0 which is recommended

 

[durbano]

Hello!
In this Proxmox I have two virtual machines, one with Windows 10 Pro and the other with Windows Server 2019 Standard.
In both cases, if I disable the qemu-guest-agent, the computer shutdown and restart commands from the GUI interface do not work.
I have updated with the latest Virtio drivers on both VMs and at the moment, the copies have been working correctly for two days.
I will continue to inform.
Thanks for your help.

 

[Dunuin]

Hello good!
In this Proxmox I have two virtual machines, one with Windows 10 Pro and the other with Windows Server 2019 Standard.
In both cases, if I disable the qemu-guest-agent, the computer shutdown and restart commands from the GUI interface do not work.
I have updated with the latest Virtio drivers on both VMs and at the moment, the copies have been working correctly for two days.
I will continue to inform.
Thanks for your help.

When not using the guest agent you will have to uncheck the "QEMU guest agent" checkbox in the VMs option tab. Then the shutdown will be done using ACPI instead of using the guest agent for that.

 

[durbano]

Thank for your respone (so fast).

I forgot to uncheck it .
If i have problems agains, i will try with this option.

Thanks a lot.