3d99082411
In addition to a single OVMF image (OVMF.fd), split images (OVMF_CODE.fd, OVMF_VARS.fd) can be used to facilitate VM management. From the OVMF Whitepaper: The variable store and the firmware executable are also available in the build output as separate files entitled: "OVMF_VARS.fd" and "OVMF_CODE.fd". This enables central management and updates of the firmware executable, while each virtual machine can retain its own variable store. An example to launch acrn-dm with the split images: --ovmf code=/usr/share/acrn/bios/OVMF_CODE.fd, \ vars=/usr/share/acrn/bios/OVMF_VARS.fd v1 -> v2: - use memory-mapped file I/O for writeback - use fcntl to lock OVMF image files Tracked-On: #5487 Signed-off-by: Peter Fang <peter.fang@intel.com> Acked-by: Wang, Yu1 <yu1.wang@intel.com> |
||
---|---|---|
.. | ||
arch/x86 | ||
bios | ||
core | ||
hw | ||
include | ||
lib | ||
log | ||
MAINTAINERS | ||
Makefile | ||
README.rst | ||
samples |
README.rst
ACRN Device Model ################# Introduction ============ The ACRN Device Model provides **device sharing** capabilities between the Service OS and Guest OSs. It is a component that is used in conjunction with the `ACRN Hypervisor`_ and this is installed within the Service OS. You can find out more about Project ACRN on the `Project ACRN documentation`_ website. .. _`ACRN Hypervisor`: https://github.com/projectacrn/acrn-hypervisor .. _`Project ACRN documentation`: https://projectacrn.github.io/