Hi Laszlo,
Thanks much for your detailed explanation. It has been very helpful.
> In order for the guest kernel to expose ACPI S3 suspend to a privileged
> guest user, the guest kernel first checks if the platform (hardware and
> firmware) support ACPI S3. This in turn depends on whether the DSDT
Public bug reported:
The issue is observed on aarch64 (I didn't check x86) with latest
upstream QEMU bits.
Steps to reproduce:
1) start guest
2) suspend guest with this command:
# echo mem > /sys/power/state
Check console messages, which should indicate that guest has been
suspended.
3) ch
" property
setter function. The check is performed only if a PCI device has been
connected to a bus, otherwise it does nothing. The latter occurs because
setter function is also called in object instantiation phase to set
property default value.
Signed-off-by: Huan Xiong
---
hw/core/qd
