libvirt/tests/qemufirmwaredata/usr/share/qemu/firmware/60-ovmf-sb.json

{
    "description": "OVMF with SB+SMM, empty varstore",
    "interface-types": [
        "uefi"
    ],
    "mapping": {
        "device": "flash",
        "mode": "split",
        "executable": {
            "filename": "/usr/share/OVMF/OVMF_CODE.secboot.fd",
            "format": "raw"
        },
        "nvram-template": {
            "filename": "/usr/share/OVMF/OVMF_VARS.fd",
            "format": "raw"
        }
    },
    "targets": [
        {
            "architecture": "x86_64",
            "machines": [
                "pc-q35-*"
            ]
        }
    ],
    "features": [
        "acpi-s3",
        "amd-sev",
        "requires-smm",
        "secure-boot",
        "verbose-dynamic"
    ],
    "tags": [

    ]
}
test: Introduce qemufirmwaretest Test firmware description parsing so far. The test files come from three locations: 1) ovmf-sb-keys.json and ovmf-sb.json come from OVMF package from RHEL-7 (with slight name change to reflect their features in filename too), 2) bios.json and aavmf.json come from example JSON documents from firmware.json from qemu's git (3a0adfc9bf), 3) ovmf.json is then copied from ovmf-sb.json and stripped of SECURE_BOOT and REQUIRES_SMM flags, OVMF path change, description update and machine type expanded for both pc and q35 machine types. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Acked-by: Laszlo Ersek <lersek@redhat.com> 2019-02-19 17:35:43 +01:00			`{`
			`"description": "OVMF with SB+SMM, empty varstore",`
			`"interface-types": [`
			`"uefi"`
			`],`
			`"mapping": {`
			`"device": "flash",`
qemu: support firmware descriptor flash 'mode' for optional NVRAM Currently the 'nvram_template' entry is mandatory when parsing the firmware descriptor based on flash. QEMU is extending the firmware descriptor spec to make the 'nvram_template' optional, depending on the value of a new 'mode' field: - "split" * "executable" contains read-only CODE * "nvram_template" contains read-write VARS - "combined" * "executable" contains read-write CODE and VARs * "nvram_template" not present - "stateless" * "executable" contains read-only CODE and VARs * "nvram_template" not present In the latter case, the guest OS can write vars but the firmware will make no attempt to persist them, so any changes will be lost at poweroff. For now we parse this new 'mode' but discard any firmware which is not 'mode=split' when matching for a domain. In the tests we have a mixture of files with and without the mode attribute. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> 2022-02-03 13:43:18 +00:00			`"mode": "split",`
test: Introduce qemufirmwaretest Test firmware description parsing so far. The test files come from three locations: 1) ovmf-sb-keys.json and ovmf-sb.json come from OVMF package from RHEL-7 (with slight name change to reflect their features in filename too), 2) bios.json and aavmf.json come from example JSON documents from firmware.json from qemu's git (3a0adfc9bf), 3) ovmf.json is then copied from ovmf-sb.json and stripped of SECURE_BOOT and REQUIRES_SMM flags, OVMF path change, description update and machine type expanded for both pc and q35 machine types. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Acked-by: Laszlo Ersek <lersek@redhat.com> 2019-02-19 17:35:43 +01:00			`"executable": {`
			`"filename": "/usr/share/OVMF/OVMF_CODE.secboot.fd",`
			`"format": "raw"`
			`},`
			`"nvram-template": {`
			`"filename": "/usr/share/OVMF/OVMF_VARS.fd",`
			`"format": "raw"`
			`}`
			`},`
			`"targets": [`
			`{`
			`"architecture": "x86_64",`
			`"machines": [`
			`"pc-q35-*"`
			`]`
			`}`
			`],`
			`"features": [`
			`"acpi-s3",`
			`"amd-sev",`
			`"requires-smm",`
			`"secure-boot",`
			`"verbose-dynamic"`
			`],`
			`"tags": [`

			`]`
			`}`