15 Feb
2013
15 Feb
'13
1:16 a.m.
On Fri, Feb 15, 2013 at 12:01:38AM +0100, Laszlo Ersek wrote:
On 02/14/13 21:55, David Woodhouse wrote:
Thanks for testing this, btw. Are you looking at suspend/resume too? :)
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!
That is strange. As noted elsewhere, on a resume or reboot the cpu should have started execution at 0xfffffff0 which is OVMF and not SeaBIOS. I don't understand why/how SeaBIOS would be involved in the resume code path at all.
-Kevin