1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00

bug fix UEFI mode

This commit is contained in:
Sabrina Jess
2022-08-05 11:28:36 -04:00
committed by openshift-cherrypick-robot
parent 72dd1a6018
commit dd7dadcede
6 changed files with 34 additions and 34 deletions

View File

@@ -3252,8 +3252,8 @@ Topics:
File: virt-configuring-certificate-rotation
- Name: Automating management tasks
File: virt-automating-management-tasks
- Name: EFI mode for virtual machines
File: virt-efi-mode-for-vms
- Name: UEFI mode for virtual machines
File: virt-uefi-mode-for-vms
- Name: Configuring PXE booting for virtual machines
File: virt-configuring-pxe-booting
- Name: Using huge pages with virtual machines

View File

@@ -1,11 +0,0 @@
// Module included in the following assemblies:
//
// * virt/virtual_machines/advanced_vm_management/virt-efi-mode-for-vms.adoc
:_content-type: CONCEPT
[id="virt-about-efi-mode-for-vms_{context}"]
= About EFI mode for virtual machines
Extensible Firmware Interface (EFI), like legacy BIOS, initializes hardware components and operating system image files when a computer starts. EFI supports more modern features and customization options than BIOS, enabling faster boot times.
It stores all the information about initialization and startup in a file with a `.efi` extension, which is stored on a special partition called EFI System Partition (ESP). The ESP also contains the boot loader programs for the operating system that is installed on the computer.

View File

@@ -0,0 +1,11 @@
// Module included in the following assemblies:
//
// * virt/virtual_machines/advanced_vm_management/virt-uefi-mode-for-vms.adoc
:_content-type: CONCEPT
[id="virt-about-uefi-mode-for-vms_{context}"]
= About UEFI mode for virtual machines
Unified Extensible Firmware Interface (UEFI), like legacy BIOS, initializes hardware components and operating system image files when a computer starts. UEFI supports more modern features and customization options than BIOS, enabling faster boot times.
It stores all the information about initialization and startup in a file with a `.efi` extension, which is stored on a special partition called EFI System Partition (ESP). The ESP also contains the boot loader programs for the operating system that is installed on the computer.

View File

@@ -1,12 +1,12 @@
// Module included in the following assemblies:
//
// * virt/virtual_machines/advanced_vm_management/virt-efi-mode-for-vms.adoc
// * virt/virtual_machines/advanced_vm_management/virt-uefi-mode-for-vms.adoc
:_content-type: PROCEDURE
[id="virt-booting-vms-efi-mode_{context}"]
= Booting virtual machines in EFI mode
[id="virt-booting-vms-uefi-mode_{context}"]
= Booting virtual machines in UEFI mode
You can configure a virtual machine to boot in EFI mode by editing the VM manifest.
You can configure a virtual machine to boot in UEFI mode by editing the `VirtualMachine` manifest.
.Prerequisites
@@ -14,9 +14,9 @@ You can configure a virtual machine to boot in EFI mode by editing the VM manife
.Procedure
. Create a YAML file that defines a VM object. Use the firmware stanza of the example YAML file:
. Edit or create a `VirtualMachine` manifest file. Use the `spec.firmware.bootloader` stanza to configure UEFI mode:
+
.Booting in EFI mode with secure boot active
.Booting in UEFI mode with secure boot active
[source,yaml]
----
apiversion: kubevirt.io/v1
@@ -45,10 +45,10 @@ spec:
bootloader:
efi:
secureBoot: true <2>
#...
...
----
<1> {VirtProductName} requires System Management Mode (`SMM`) to be enabled for Secure Boot in EFI mode to occur.
<2> {VirtProductName} supports a VM with or without Secure Boot when using EFI mode. If Secure Boot is enabled, then EFI mode is required. However, EFI mode can be enabled without using Secure Boot.
<1> {VirtProductName} requires System Management Mode (`SMM`) to be enabled for Secure Boot in UEFI mode to occur.
<2> {VirtProductName} supports a VM with or without Secure Boot when using UEFI mode. If Secure Boot is enabled, then UEFI mode is required. However, UEFI mode can be enabled without using Secure Boot.
. Apply the manifest to your cluster by running the following command:
+

View File

@@ -1,12 +0,0 @@
:_content-type: ASSEMBLY
[id="virt-efi-mode-for-vms"]
= Using EFI mode for virtual machines
include::_attributes/common-attributes.adoc[]
:context: virt-efi-mode-for-vms
toc::[]
You can boot a virtual machine (VM) in Extensible Firmware Interface (EFI) mode.
include::modules/virt-about-efi-mode-for-vms.adoc[leveloffset=+1]
include::modules/virt-booting-vms-efi-mode.adoc[leveloffset=+1]

View File

@@ -0,0 +1,12 @@
:_content-type: ASSEMBLY
[id="virt-uefi-mode-for-vms"]
= Using UEFI mode for virtual machines
include::_attributes/common-attributes.adoc[]
:context: virt-uefi-mode-for-vms
toc::[]
You can boot a virtual machine (VM) in Unified Extensible Firmware Interface (UEFI) mode.
include::modules/virt-about-uefi-mode-for-vms.adoc[leveloffset=+1]
include::modules/virt-booting-vms-uefi-mode.adoc[leveloffset=+1]