On Fri, 2013-02-15 at 00:01 +0100, Laszlo Ersek wrote:
Entering S3 seemed OK (except the screen was not cleared; using Cirrus). I woke up the guest with
# virsh qemu-monitor-command fw-ovmf.g-f18xfce2012121716.e-rhel63 \ --hmp --cmd system_wakeup
Trailing portion of the log:
In resume (status=254) In 32bit resume rsdp=0x00000000 No resume vector set! Attempting a hard reboot i8042_wait_write In resume (status=0) In 32bit resume Attempting a hard reboot [...]
I can see the following CSM calls earlier:
- Legacy16InitializeYourself
- Legacy16GetTableAddress
- Legacy16DispatchOprom
- Legacy16UpdateBbs
No calls to PrepareToBoot (which could set RsdpAddr); this is an UEFI guest. (The CSM is used for the GOP only.)
So you have the same problem as with reset — you're ending up back in the CSM in RAM, when you ought to be in the OVMF "ROM".
I wonder if a *Legacy* guest might actually fare a little better? At least find_resume_vector() would have a chance of working if the CSM has actually been told where the ACPI tables are...