Lines Matching +full:qemu +full:- +full:x86_64

1 # -*- Mode: Python -*-
11 # later. See the COPYING file in the top-level directory.
18 'member-name-exceptions': [
19 'FirmwareArchitecture' # x86_64
25 # Lists the firmware-OS interface types provided by various firmware
26 # that is commonly used with QEMU virtual machines.
32 # 1275-1994 standard. Examples for firmware projects that
35 # @uboot: Firmware interface defined by the U-Boot project.
68 # Enumeration of architectures for which Qemu uses additional
71 # @aarch64: 64-bit Arm.
73 # @arm: 32-bit Arm.
75 # @i386: 32-bit x86.
77 # @loongarch64: 64-bit LoongArch. (since: 7.1)
79 # @x86_64: 64-bit x86.
84 'data' : [ 'aarch64', 'arm', 'i386', 'loongarch64', 'x86_64' ] }
91 # @architecture: Determines the emulation target (the QEMU system
99 # (For example, the glob pattern "pc-i440fx-*" matches
100 # "pc-i440fx-2.12".) On the QEMU command line, "-machine
116 # @acpi-s3: The firmware supports S3 sleep (suspend to RAM), as defined
117 # in the ACPI specification. On the "pc-i440fx-*" machine
118 # types of the @i386 and @x86_64 emulation targets, S3 can be
119 # enabled with "-global PIIX4_PM.disable_s3=0" and disabled
120 # with "-global PIIX4_PM.disable_s3=1". On the "pc-q35-*"
121 # machine types of the @i386 and @x86_64 emulation targets, S3
122 # can be enabled with "-global ICH9-LPC.disable_s3=0" and
123 # disabled with "-global ICH9-LPC.disable_s3=1".
125 # @acpi-s4: The firmware supports S4 hibernation (suspend to disk), as
126 # defined in the ACPI specification. On the "pc-i440fx-*"
127 # machine types of the @i386 and @x86_64 emulation targets, S4
128 # can be enabled with "-global PIIX4_PM.disable_s4=0" and
129 # disabled with "-global PIIX4_PM.disable_s4=1". On the
130 # "pc-q35-*" machine types of the @i386 and @x86_64 emulation
131 # targets, S4 can be enabled with "-global
132 # ICH9-LPC.disable_s4=0" and disabled with "-global
133 # ICH9-LPC.disable_s4=1".
135 # @amd-sev: The firmware supports running under AMD Secure Encrypted
137 # Programmer's Manual. QEMU command line options related to
139 # "docs/system/i386/amd-memory-encryption.rst".
141 # @amd-sev-es: The firmware supports running under AMD Secure Encrypted
142 # Virtualization - Encrypted State, as specified in the AMD64
143 # Architecture Programmer's Manual. QEMU command line options
145 # "docs/system/i386/amd-memory-encryption.rst".
147 # @amd-sev-snp: The firmware supports running under AMD Secure Encrypted
148 # Virtualization - Secure Nested Paging, as specified in the
149 # AMD64 Architecture Programmer's Manual. QEMU command line
151 # "docs/system/i386/amd-memory-encryption.rst".
153 # @intel-tdx: The firmware supports running under Intel Trust Domain
156 # @enrolled-keys: The variable store (NVRAM) template associated with
161 # @requires-smm: The firmware requires the platform to emulate SMM
164 # and IA-32 Architectures Software Developer's Manual. On
165 # the "pc-q35-*" machine types of the @i386 and @x86_64
167 # "-machine smm=on". (On the "pc-q35-*" machine types of
168 # the @i386 emulation target, @requires-smm presents
170 # is "-cpu coreduo,nx=off".) If the firmware is marked as
171 # both @secure-boot and @requires-smm, then write
174 # in SMM, using the additional option "-global
176 # Furthermore, a large guest-physical address space
177 # (comprising guest RAM, memory hotplug range, and 64-bit
180 # the "pc-q35-*" machine types of the @i386 and @x86_64
182 # above the default 16MB with the "-global
183 # mch.extended-tseg-mbytes=uint16" option. As a rule of
185 # guest-phys address space and a few tens of VCPUs; for
186 # every further TB of guest-phys address space, add 8MB
187 # of SMRAM. 48MB should suffice for 4TB of guest-phys
188 # address space and 2-3 hundred VCPUs.
190 # @secure-boot: The firmware implements the software interfaces for UEFI
192 # that without @requires-smm, guest code running with
196 # @verbose-dynamic: When firmware log capture is enabled, the firmware
200 # "pc-i440fx-*" and "pc-q35-*" machine types of the
201 # @i386 and @x86_64 emulation targets, firmware log
202 # capture can be enabled with the QEMU command line
203 # options "-chardev file,id=fwdebug,path=LOGFILEPATH
204 # -device isa-debugcon,iobase=0x402,chardev=fwdebug".
205 # @verbose-dynamic is mutually exclusive with
206 # @verbose-static.
208 # @verbose-static: The firmware unconditionally produces a large amount
211 # firmware for the "virt-*" machine types of the @arm
214 # PL011 UART. @verbose-static is mutually exclusive
215 # with @verbose-dynamic.
220 'data' : [ 'acpi-s3', 'acpi-s4',
221 'amd-sev', 'amd-sev-es', 'amd-sev-snp',
222 'intel-tdx',
223 'enrolled-keys', 'requires-smm', 'secure-boot',
224 'verbose-dynamic', 'verbose-static' ] }
244 # file into a pflash chip. The corresponding QEMU command line option is
245 # "-drive file=@filename,format=@format". Note however that the
246 # option-argument shown here is incomplete; it is completed under
252 # @format: Specifies the block format of the file pointed-to by
270 # must be configured read-only and can be shared between
272 # for each new guest and configured read-write.
276 # for each new guest and configured read-write.
281 # be configured read-only and can be shared
303 # corresponding QEMU command line options are
304 # -drive if=none,id=pflash0,readonly=on,file=@executable.@filename,format=@executa…
305 # -machine pflash0=pflash0
306 # or equivalent -blockdev instead of -drive. When
309 # With QEMU versions older than 4.0, you have to use
310 # -drive if=pflash,unit=0,readonly=on,file=@executable.@filename,format=@executabl…
312 # @nvram-template: Identifies the NVRAM template compatible with
316 # individual copy -- a specific NVRAM file -- from
317 # @nvram-template.@filename for each new virtual
318 # machine definition created. @nvram-template.@filename
322 # non-volatile UEFI variables of a virtual machine
323 # definition. The preferred corresponding QEMU
325 # -drive if=none,id=pflash1,readonly=off,file=FILENAME_OF_PRIVATE_NVRAM_FILE,f…
326 # -machine pflash1=pflash1
327 # or equivalent -blockdev instead of -drive.
328 # With QEMU versions older than 4.0, you have to use
329 # -drive if=pflash,unit=1,readonly=off,file=FILENAME_OF_PRIVATE_NVRAM_FILE,for…
336 '*nvram-template' : 'FirmwareFlashFile' } }
346 # corresponding QEMU command line option is "-kernel
362 # corresponding QEMU command line option is "-bios
399 # single @Firmware root element) with a double-digit prefix, for example
400 # "50-ovmf.json", "50-seabios-256k.json", etc, so they can be sorted in
404 # - /usr/share/qemu/firmware -- populated by distro-provided firmware
408 # - /etc/qemu/firmware -- exclusively for sysadmins' local additions,
410 # - $XDG_CONFIG_HOME/qemu/firmware -- exclusively for per-user local
414 # Top-down, the list of directories goes from general to specific.
426 # - /usr/share/qemu/firmware/50-ovmf.json
428 # - /usr/share/qemu/firmware/50-seabios-256k.json
432 # $ touch /etc/qemu/firmware/50-ovmf.json
436 # $ vim /etc/qemu/firmware/50-ovmf.json
440 # $ vim /etc/qemu/firmware/10-ovmf.json
444 # $ vim /etc/qemu/firmware/99-ovmf.json
446 # @description: Provides a human-readable description of the firmware.
449 # @interface-types: Lists the types of interfaces that the firmware can
450 # expose to the guest OS. This is a non-empty, ordered
451 # list; entries near the beginning of @interface-types
455 # @interface-types.
459 # @targets: Collects the target architectures (QEMU system emulators)
467 # possible exposure to the end-user. @tags serves development and
473 # .. qmp-example::
477 # "interface-types": [
482 # "filename": "/usr/share/seabios/bios-256k.bin"
488 # "pc-i440fx-*",
489 # "pc-q35-*"
493 # "architecture": "x86_64",
495 # "pc-i440fx-*",
496 # "pc-q35-*"
501 # "acpi-s3",
502 # "acpi-s4"
513 # "interface-types": [
522 # "nvram-template": {
529 # "architecture": "x86_64",
531 # "pc-q35-*"
536 # "acpi-s3",
537 # "amd-sev",
538 # "requires-smm",
539 # "secure-boot",
540 # "verbose-dynamic"
543 # "-a IA32",
544 # "-a X64",
545 # "-p OvmfPkg/OvmfPkgIa32X64.dsc",
546 # "-t GCC48",
547 # "-b DEBUG",
548 # "-D SMM_REQUIRE",
549 # "-D SECURE_BOOT_ENABLE",
550 # "-D FD_SIZE_4MB"
556 # "interface-types": [
565 # "nvram-template": {
572 # "architecture": "x86_64",
574 # "pc-q35-*"
579 # "acpi-s3",
580 # "amd-sev",
581 # "enrolled-keys",
582 # "requires-smm",
583 # "secure-boot",
584 # "verbose-dynamic"
587 # "-a IA32",
588 # "-a X64",
589 # "-p OvmfPkg/OvmfPkgIa32X64.dsc",
590 # "-t GCC48",
591 # "-b DEBUG",
592 # "-D SMM_REQUIRE",
593 # "-D SECURE_BOOT_ENABLE",
594 # "-D FD_SIZE_4MB"
599 # "description": "OVMF with SEV-ES support",
600 # "interface-types": [
609 # "nvram-template": {
616 # "architecture": "x86_64",
618 # "pc-q35-*"
623 # "acpi-s3",
624 # "amd-sev",
625 # "amd-sev-es",
626 # "verbose-dynamic"
629 # "-a X64",
630 # "-p OvmfPkg/OvmfPkgX64.dsc",
631 # "-t GCC48",
632 # "-b DEBUG",
633 # "-D FD_SIZE_4MB"
639 # "interface-types": [
648 # "nvram-template": {
657 # "virt-*"
665 # "-a AARCH64",
666 # "-p ArmVirtPkg/ArmVirtQemu.dsc",
667 # "-t GCC48",
668 # "-b DEBUG",
669 # "-D DEBUG_PRINT_ERROR_LEVEL=0x80000000"
675 'interface-types' : [ 'FirmwareOSInterface' ],