UEFI has been around for over 15 years now, and with hardware now coming out that lacks support for the UEFI CSM for legacy BIOS boot support, we should change our virtualization stack defaults so that UEFI is used by default.
This change would also align with the upcoming release of Microsoft Windows 11, which only supports UEFI with Secure Boot. The general expectation will be that people shouldn't need to fiddle with such things to make working machines. With KVM and Xen through virt-manager; virt-install; gnome-boxes; and cockpit-machines, we should have UEFI as the default so that things work.
virt-manager
virt-install
gnome-boxes
cockpit-machines
Ideally, for UEFI boot by default, UEFI boot should also include CSM support, so that it's transparent and legacy stuff works too.
Metadata Update from @Pharaoh_Atem: - Custom field SUSE Jira adjusted to https://jira.suse.com/browse/OPENSUSE-52 - Issue set to the milestone: 15.4
Hello,
SUSE's take on the request is following
+- jsc#SLE-21540 Dev: Prefer UEFI when creating new virtual machines. + Add a preferences option to allow users to default to UEFI when + creating a new VM. Libvirt decides which firmware file to use. + virtman-add-firmware-preferences.patch +- Renamed patch virtinst-modify-gui-defaults.patch to + virtman-modify-gui-defaults.patch
This was already released as part virt-manager in 15 SP4 GA
SLE Micro / cockpit-machines request is https://jira.suse.com/browse/SMO-224
Metadata Update from @lkocman: - Custom field SUSE Jira - SUSE Linux Enterprise adjusted to https://jira.suse.com/browse/SMO-224
Login to comment on this ticket.