catborise 005fa59bf0 feat(instances): a new VM can have UEFI Secure Boot and a TPM 2.0 ... Windows 11 does not install without Secure Boot and a TPM 2.0, and the new VM form offered neither: its firmware list was BIOS and one UEFI loader guessed from file names, which on RHEL never matched the Secure Boot one. The firmware choices are now BIOS, UEFI and UEFI Secure Boot, as the host's libvirt reports them (its firmware features from libvirt 12.1, before that its loaders), and libvirt picks the firmware itself: UEFI without Secure Boot, or with Microsoft's keys enrolled. A TPM 2.0 switch, shown when the host has swtpm, adds an emulated TPM. The create job refuses a firmware or a TPM the host does not offer, and the API takes both. The path-guessing helpers are gone.		2026-11-01 16:18:29 +03:00
..
cz/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
de/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
en/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
es/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
fr/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
ru/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
tr/LC_MESSAGES	feat(instances): a new VM can have UEFI Secure Boot and a TPM 2.0	2026-11-01 16:18:29 +03:00
uk/LC_MESSAGES	update locales and tr translations	2024-02-14 09:19:29 +03:00
zh/LC_MESSAGES	update translation for zh	2023-12-13 14:03:00 +08:00