Problem
My computer reboots when selecting suspend (or running systemctl suspend in dom0) after using different VMs for some time.
Additional Context
When operating very basic tasks (e.g., opening thunar), suspend works fine.
However, when working across different qubes for a while with moderate activity (e.g., editing a document, browsing the web, etc.), suspend leads to reboot. This applies also when shutting down all non-service related qubes before suspending.
The system can be up and running for a whole day, with little to no activity, and suspend works fine. However, as soon as activities add up (even if shutting them down afterward), suspend leads to reboot.
Selecting the latest or an older kernel in dom0 makes no difference.
I have the same qubes templates/VMs running on a laptop, where suspend works fine.
Hardware
Lenovo Thinkstation P360 Ultra, 32 GB RAM, 12th Gen Intel(R) Core™ i7-12700K
The computer’s manual says:
“Power management: Hibernation / Suspend to Disk / ACPI S4 and Sleep / Suspend to RAM / ACPI S3 are NOT supported on this system.”
Does this mean that I need to switch to suspend-to-idle (“S0ix”), and that this is my only option? If so, does anyone happen to know why I can suspend before using the computer for some time (e.g., after booting sys-qubes and starting one or two AppVM’s file managers)
Any help in getting suspend to work reliably, if possible, would be very much appreciated. Thanks!