diff options
| author | Andrea Bolognani <abologna@redhat.com> | 2022-12-12 19:32:32 +0100 |
|---|---|---|
| committer | Cole Robinson <crobinso@redhat.com> | 2023-02-09 11:41:00 -0500 |
| commit | f2b5aaf458764ec7ecf105038e5f2f7cc26b6c17 (patch) | |
| tree | 679d38ad00dea447d9638087d32bf7d8663d2a00 /man | |
| parent | a63b40aae3835a8b82b23755f1ed45e526af80f9 (diff) | |
| download | virt-manager-f2b5aaf458764ec7ecf105038e5f2f7cc26b6c17.tar.gz | |
virt-install: Recommend '--boot uefi'
Firmware autoselection is the way to go in most cases, so
recommend that instead of telling users that they should provide
all information manually.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Diffstat (limited to 'man')
| -rw-r--r-- | man/virt-install.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man/virt-install.rst b/man/virt-install.rst index 3a6e8dcd..684f2265 100644 --- a/man/virt-install.rst +++ b/man/virt-install.rst @@ -955,13 +955,13 @@ Some examples: Configure the VM to boot from UEFI. In order for virt-install to know the correct UEFI parameters, libvirt needs to be advertising known UEFI binaries via domcapabilities XML, so this will likely only work if using properly - configured distro packages. + configured distro packages. This is the recommended UEFI setup. ``--boot loader=/.../OVMF_CODE.fd,loader.readonly=yes,loader.type=pflash,nvram.template=/.../OVMF_VARS.fd,loader_secure=no`` Specify that the virtual machine use the custom OVMF binary as boot firmware, mapped as a virtual flash chip. In addition, request that libvirt instantiate the VM-specific UEFI varstore from the custom "/.../OVMF_VARS.fd" varstore - template. This is the recommended UEFI setup, and should be used if + template. This setup is not recommended, and should only be used if --boot uefi doesn't know about your UEFI binaries. If your UEFI firmware supports Secure boot feature you can enable it via loader_secure. |