Update packages file for version 25880

Signed-off-by: clrbuilder <clrbuilder@intel.com>
start_qemu.sh: enable OVMF CODE and VARS usage
2026-06-16 11:06:15 +00:00 · 2018-10-26 00:32:14 +00:00 · 2018-10-25 16:44:58 -05:00 · 2018-10-25 21:32:21 +00:00 · 2018-10-25 15:36:19 -05:00
4 changed files with 12 additions and 1 deletions
@@ -1048,6 +1048,7 @@ clr-find-bundle
 clr-fwupd-hooks
 clr-hardware-files
 clr-init
+clr-installer
 clr-man-pages
 clr-power-tweaks
 clr-python-timestamp
@@ -2936,6 +2937,7 @@ perl-Test-Manifest
 perl-Test-MockModule
 perl-Test-MockTime
 perl-Test-More-UTF8
+perl-Test-Most
 perl-Test-Needs
 perl-Test-NoWarnings
 perl-Test-Number-Delta
@@ -2952,6 +2954,7 @@ perl-Test-Strict
 perl-Test-Synopsis
 perl-Test-TCP
 perl-Test-Taint
+perl-Test-Trap
 perl-Test-UseAllModules
 perl-Test-Warn
 perl-Test-Warnings
@@ -43,11 +43,19 @@ if [ ! -f "$IMAGE" ]; then
 fi
 rm -f debug.log

+# 10/25/2018: keep back compatibility for a while
+UEFI_BIOS="-bios OVMF.fd"
+
+if [ -f OVMF_VARS.fd -a -f OVMF_CODE.fd ]; then
+    UEFI_BIOS=" -drive file=OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on "
+    UEFI_BIOS+=" -drive file=OVMF_VARS.fd,if=pflash,format=raw,unit=1 "
+fi
+
 VMN=${VMN:=1}

 qemu-system-x86_64 \
    -enable-kvm \
-    -bios OVMF.fd \
+    ${UEFI_BIOS} \
    -smp sockets=1,cpus=4,cores=2 -cpu host \
    -m 1024 \
    -vga none -nographic \
Author	SHA1	Message	Date
clrbuilder	36d3edd56c	Update packages file for version 25880 Signed-off-by: clrbuilder <clrbuilder@intel.com>	2018-10-26 00:32:14 +00:00
Miguel Bernal Marin	9008cbccba	start_qemu.sh: enable OVMF CODE and VARS usage Currently, we use the traditional BIOS flag "-bios" to specify the OVMF firmware device file. Ken proposes changing to pflash type BIOS and separate BIOS code and variable. -drive file=OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on \ -drive file=OVMF_VARS.fd,if=pflash,format=raw,unit=1 \ Ken has following reasons: 1. -bios can only support single flash binary, but the actual BIOS binary is consisted by many parts like SEC, PEI(Boot Block), DXE(Main Block) and Variable area as non-volatile storage for BIOS settings. During OMVF booting, a file called NvVars.bin will be created at <Disk>/<ESP Partition>/NvVars.bin for BIOS variable storage. This will pollute original Clearlinux-xxx.img. 2. In future, we can add secure signed SEC BIOS part to enable full secure boot for Clear Linux via pflash. 3. Some version of open stack, it requires separate Var Store NV instead of OVMF.fd. Ken meet with this issue recently. So if can show the separate pflash BIOS file via start_qemu.sh as example. Suggested-by: "Lu, Ken" <ken.lu@intel.com>	2018-10-25 16:44:58 -05:00
clrbuilder	04022fb765	Update packages file for version 25870 Signed-off-by: clrbuilder <clrbuilder@intel.com>	2018-10-25 21:32:21 +00:00
Miguel Bernal Marin	424c34140e	Add OVMF CODE and VARS to repo As from `0c69bfb9a9` ("Add OVMF.fd to the repo"), the CODE and VARS will be used by start_qemu.sh. Note that these version of OVMF_* are a copy from /usr/share/qemu in Clear Linux OS 25840. $ sha512sum /usr/share/qemu/OVMF_* efea56944ad8153ed956390863c30c1a61eb4e52c43a8a0e3e6e3a71e56796f3c6a1c32e107a3d86e7a2e59faa462c7ffb10916b62a73d110bd0b0b84a60e02a /usr/share/qemu/OVMF_CODE.fd 448412fd7ba267b4180db8ade6edb67af467e5b9b3e3ff8dfd583a2fded4070f6951667297e6896ce8bd9f4d2ec3dd8a5a70b6e9a2f686efec9a57124fec512a /usr/share/qemu/OVMF_VARS.fd	2018-10-25 15:36:19 -05:00