Doing "systemctl status qubes-suspend.service" shows suspend as loaded and inactive(dead)
Doing "journalctl -u qubes-suspend.service" shows
"Dom0 systemd[1]: starting Qubes suspend hooks ...
Dom0 systemd[1]: qubes-suspend.service: Main process exited, code=exited, status=203/EXEC
Dom0 systemd[1]: Failed to start Qubes suspend hooks.
Dom0 systemd[1]: qubes-suspend.service: Unit entered failed state
Dom0 systemd[1]: qubes-suspend.service: Failed with result 'exit-code'."
In terminal to check mem_sleep value "sudo cat /sys/power/men_sleep " shows deep selected "s2idle [deep]"
"-- Reboot --
Dom0 systemd[1]: Starting Qubes suspend hooks ...
Dom0 52qubes-pause-vms[12838]: 0
Dom0 systems[1]: Started Qubes suspend hooks.
--Reboot--
Dom0 systemd[1]: qubes-suspend. Service: Unit not needed anymore. stopping"
It looks like suspend hook worked but I am not sure could it the resume hook" since it shuts off after exec suspend hook?
For me suspend worked properly in R3.2, but on R4 I have the same problem with suspend, shutting down instead. But only with AEM boot, if I boot without AEM, suspend works again.