Best practise on Windows Server Hibernate/suspend-disk/resume or guest-acpi-* ?

[Timo Goetze]

Hi,
does anyone has best practise doc about hibernating Windows Servers?

The reason why this is important to us is, that we want to switch from shutting down engines to hibernate and first tests showed that it seems to be tricky and depending on virtio versions/guesttools version and virtual hardware. Usecase is "powerfail" and things need to be fast on UPS battery.

We have windows 2016 and 2019 and 2022 servers. Our linux VMs are no problem.

Does anyone has best practise which configuration doesnt end in VM stalling during suspend or resume.

we tried sequentially qm suspend [VMID] --todisk and qm guest cmd suspend-disk ... both not 100% satisfying on some windows server. some work hassle free, some work sometimes, some dont suspend or are unresumable after a suspend.


Thanks for Ideas or tips

Cheers, Timo

 

[apoc]

Does anyone has best practise which configuration doesnt end in VM stalling during suspend or resume.

Dont use suspend/resume for servers.
This concept comes from windows clients.

Everything server wise does not like it much, especially when an AD is involved.
Time sync is critical, time jumps are not good/accepted. Kerberos for instance is very picky on time.
Do proper guest is shutdowns in the right order.
This is the only thing that works properly.

 

[pille99]

Dont use suspend/resume for servers.
This concept comes from windows clients.

Everything server wise does not like it much, especially when an AD is involved.
Time sync is critical, time jumps are not good/accepted. Kerberos for instance is very picky on time.
Do proper guest is shutdowns in the right order.
This is the only thing that works properly.

a server is never "suspended" and "resumed". server runs all the time. if you dont need your server for a while, shutdown the server on the regular way. i completely agree with apoc