Guest agent not running on Windows 11

[IsThisThingOn]

Not sure if I can follow what you mean.
PBS is not slow, but PVE there is. HPEproliant microserver gen 10 with two SSDs in mirror plus a very slow copper upload connection.

 

[_gabriel]

sorry for my poor english wording...
do you backup directly over WAN ?

 

[_gabriel]

Reminder : during backup, I/O writes are sent to PBS before within guest itself, it's a "copy-before-write" méthode.
There is fleecing option to mitigate.

 

[_gabriel]

if downtime isn't critical, if whole reading source isn't too long, the safest is
schedule shutdown guest, then backup offline, then start guest after Backup done using hook script

 

[SteveITS]

Yes, since the backup is at 01:00.
I think that the system gets shut down for backup, boots up again and then for some reasons these two services won't start.

The Windows event log should have an entry if they fail to start or crash.

You could always create a Scheduled Task in Windows to start the services at startup. “Sc start servicename”

 

[Puliper]

The Windows 11 QEMU guest agent stops because during stop-mode backups, the VM pauses and if Proxmox Backup Server is slower than the guest’s I/O, services like QEMU-GA and SQLWriter can fail to start, causing timeouts. Downgrading Virtio guest tools to 0.1.271 or using snapshot/suspend mode for backups usually fixes it, and the agent may need a manual restart if it doesn’t start automatically.

 

[_gabriel]

using snapshot/suspend mode for backups usually fixes it

not really fixes as snapshot is done during stop mode too.
Stop mode can be more impacted because many I/O can be done during boot.

 

[uzumo]

If it happens during OS startup, wouldn't extending the timeout be the solution?

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control /v ServicesPipeTimeout /t REG_DWORD /d 120000

*We don't recommend using services that can't be started infinitely, as it takes time to discover when problems occur. However, if you're certain the service you're using isn't one of those, changing it shouldn't cause any issues.

If 120 seconds doesn't work, try specifying 360 seconds (360000) and see how long it takes to boot up.