mirror of
https://anongit.gentoo.org/git/repo/gentoo.git
synced 2025-06-13 16:42:39 +02:00
33a4360bc3
The filenames used here differ from Fedora, which ships far more variants. I felt it unnecessary to include the raw and unpadded images when the padded QCOW2 images should be all you need. QEMU_EFI.secboot_INSECURE.qcow2 does have Secure Boot enabled, but it must not be used in production. The lack of an SMM implementation for arm64 in this firmware means that the EFI variable store is unprotected, making the firmware unsafe. Signed-off-by: James Le Cuirot <chewi@gentoo.org>
33 lines
785 B
JSON
33 lines
785 B
JSON
{
|
|
"description": "UEFI for arm64 VMs, with *INSECURE* SB, SB enabled, MS certs enrolled",
|
|
"interface-types": [
|
|
"uefi"
|
|
],
|
|
"mapping": {
|
|
"device": "flash",
|
|
"mode" : "split",
|
|
"executable": {
|
|
"filename": "/usr/share/edk2/ArmVirtQemu-AARCH64/QEMU_EFI.secboot_INSECURE.qcow2",
|
|
"format": "qcow2"
|
|
},
|
|
"nvram-template": {
|
|
"filename": "/usr/share/edk2/ArmVirtQemu-AARCH64/QEMU_VARS.secboot_INSECURE.qcow2",
|
|
"format": "qcow2"
|
|
}
|
|
},
|
|
"targets": [
|
|
{
|
|
"architecture": "aarch64",
|
|
"machines": [
|
|
"virt-*"
|
|
]
|
|
}
|
|
],
|
|
"features": [
|
|
"enrolled-keys",
|
|
"secure-boot"
|
|
],
|
|
"tags": [
|
|
|
|
]
|
|
}
|