mirror of
https://github.com/projectacrn/acrn-hypervisor.git
synced 2026-05-04 09:54:52 +00:00
b240450064
With current code, the acrn.efi is inserted between cl bootloader.efi and bzImage.efi that destroyed the chain relationship of cl bootloader and cl bzImage.efi. And the following is current boot flow: UEFI -> cl bootloader.efi -> acrn.efi -> bzImage.efi The purpose of this patch is resume above chain relationship, and make uefi vm return to efi stub context once launched, then continue to call the UEFI API(LoadImage/StartImage) to launch cl bootloader or other bootloaders. So the boot flow will change to be as below: UEFI -> acrn.efi -> cl bootloader.efi -> bzImage.efi After applying this patch, the code related to loading bzImage.efi and getting pe_entry is unnecessary due to the bzImage.efi will not be launched by acrn.efi directly, so it is removed. Signed-off-by: Zheng, Gen <gen.zheng@intel.com>
Embedded-Hypervisor ################### This open source embedded hypervisor defines a software architecture for running multiple software subsystems managed securely on a consolidated system (by means of a virtual machine manager), and defines a reference framework Device Model implementation for devices emulation This embedded hypervisor is type-1 reference hypervisor, running directly on the system hardware. It can be used for building software defined cockpit (SDC) or In-Vehicle Experience (IVE) solutions running on Intel Architecture Apollo Lake platforms. As a reference implementation, it provides the basis for embedded hypervisor vendors to build solutions with an open source reference I/O mediation solution, and provides auto makers a reference software stack for SDC usage. This embedded hypervisor is able to support both Linux* and Android* as a Guest OS, managed by the hypervisor, where applications can run. This embedded hypervisor is a partitioning hypervisor reference stack, also suitable for non-automotive IoT & embedded device solutions. It will be addressing the gap that currently exists between datacenter hypervisors, hard partitioning hypervisors, and select industrial applications. Extending the scope of this open source embedded hypervisor relies on the involvement of community developers like you!