Discussion:
[edk2] OVMF cannot boot in QEMU 1.6.2
Ni, Ruiyu
2015-07-07 06:47:54 UTC
Permalink
Hi,
I found OVMF built from the latest source tree cannot boot in QEMU 1.6.2 (Ubuntu14.04.1).
Is it related to the changes made to OvmfPkg?
Boot log as following:
------------------
SecCoreStartupWithStack(0xFFFCC000, 0x818000)
Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE
Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is 0x0
Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38
Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6
Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389

ASSERT_EFI_ERROR (Status = Invalid Parameter)
ASSERT /home/ray/work/AllPackagesDev/MdeModulePkg/Core/Pei/Image/Image.c(580): !EFI_ERROR (Status)

Regards,
Ray
Laszlo Ersek
2015-07-07 12:35:42 UTC
Permalink
Post by Ni, Ruiyu
Hi,
I found OVMF built from the latest source tree cannot boot in QEMU 1.6.2 (Ubuntu14.04.1).
Is it related to the changes made to OvmfPkg?
I can't tell offhand if this is a bug in that old version of QEMU.

Your QEMU command line could also be problematic; can you share it?
Post by Ni, Ruiyu
------------------
SecCoreStartupWithStack(0xFFFCC000, 0x818000)
Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE
Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is 0x0
this looks broken already; the handle here should never be NULL.
(Printed by "MdeModulePkg/Core/Pei/FwVol/FwVol.c" somewhere.)

Thanks
Laszlo
Post by Ni, Ruiyu
Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38
Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6
Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389
ASSERT_EFI_ERROR (Status = Invalid Parameter)
ASSERT
!EFI_ERROR (Status)
Ni, Ruiyu
2015-07-09 07:20:39 UTC
Permalink
Laszlo,
Thanks for the suggestion.
I root caused the issue (see attachment).

Thanks,
Ray
-----Original Message-----
Sent: Tuesday, July 7, 2015 8:36 PM
Subject: Re: [edk2] OVMF cannot boot in QEMU 1.6.2
Post by Ni, Ruiyu
Hi,
I found OVMF built from the latest source tree cannot boot in QEMU 1.6.2
(Ubuntu14.04.1).
Is it related to the changes made to OvmfPkg?
I can't tell offhand if this is a bug in that old version of QEMU.
Your QEMU command line could also be problematic; can you share it?
Post by Ni, Ruiyu
------------------
SecCoreStartupWithStack(0xFFFCC000, 0x818000)
Register PPI Notify: DCD0BE23-9586-40F4-B643-06522CED4EDE
Install PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Install PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
The 0th FV start address is 0x00000820000, size is 0x000E0000, handle is
0x0
this looks broken already; the handle here should never be NULL.
(Printed by "MdeModulePkg/Core/Pei/FwVol/FwVol.c" somewhere.)
Thanks
Laszlo
Post by Ni, Ruiyu
Register PPI Notify: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Register PPI Notify: EA7CA24B-DED5-4DAD-A389-BF827E8F9B38
Install PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6
Install PPI: DBE23AA9-A345-4B97-85B6-B226F1617389
ASSERT_EFI_ERROR (Status = Invalid Parameter)
ASSERT
/home/ray/work/AllPackagesDev/MdeModulePkg/Core/Pei/Image/Image.c(
Post by Ni, Ruiyu
!EFI_ERROR (Status)
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Loading...