rtcwake / acpi capabilities

[Flyer]

Hi all,
this is my first post over Proxmox forum

Back to my post title, currently using Proxmox mixing containers and VMs, one of these is a Rockstor (Centos 7 btrfs nas system) development environment.
I was working on a new feature (system custom scheduled tasks like reboot, shutdown and user custom crons) and obviously had no issues with system reboots, not the same over system shutdowns:
system shutdown itself is ok, but with rtcwake things get harder

rtcwake -m mem -s 120

wake up OK, system suspend to RAM and wake after 120 secs (ACPI S3)

rtcwake -m disk -s 120

wake up FAILS, system suspend to disk (S4)

rtcwake -m off-s 120

wake up FAILS, system power off (S5)

rtcwake -m freeze -s 120

odds, system seems running, but no console

Notes: BIOS = SeaBIOS, dmidecode has no BIOS info

Do you have any suggestion ?

Thanks
Mirko

P.S.: I know a Proxmox VM has no real hwclock, but if S3 runs our emulated hwclock is working

 

[Richard]

rtcwake -m mem -s 120

wake up OK, system suspend to RAM and wake after 120 secs (ACPI S3)

rtcwake -m disk -s 120

wake up FAILS, system suspend to disk (S4)

Cannot work - when a VM is powered off it does not exist any more (and now rtc is present)

rtcwake -m off-s 120

wake up FAILS, system power off (S5)

same as above

rtcwake -m freeze -s 120

odds, system seems running, but no console

"freeze" function is not an ACPI feature

Notes: BIOS = SeaBIOS, dmidecode has no BIOS info

SeaBIOS cannot be compared with a real HW BIOS regarding these features.