Re: oVirt/RHV 4.3.6: How to boot a Q35/UEFI VM from CD?
I have successfully managed to boot and install RHEL & openSUSE with Secureboot, but UEFI variables are not saved and requires some workarounds (there is a bug opened for that) to work. What exactly is your problem? Best Regards, Strahil NikolovOn Oct 29, 2019 10:32, mathieu.simon@gymneufeld.ch wrote:
Hi
I've been experimenting with UEFI on RHV 4.3.6 using Windows Server 2019 but I guess posting on the oVirt list might reach a wider audience. I've used UEFI guests on other KVM-based virtualizations, but I have been unable to detect a UEFI-bootable CD using Q35 VMs with or without SecureBoot in RHV 4.3.6 since it doesn't even propose to load the UEFI loader from within OVMF. It seems to show the CD-ROM drive, but I cannot boot from file the disc from OVMF:
Are there any hints? (I've tried finding something more detailed in the Docs though) I'd like investigate UEFI and SecureBoot on oVirt/RHV even if it's still considered a tech preview. (I've been using KVM-based UEFI VM for years already on other platforms and distributions with no particular issues, rather advantages overall).
Regards Mathieu _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AVHRXTQ4TSZCYA...
What exactly is your problem? In all cases booting the VM with a Windows boot disc no disc is detected, variants are shown When I boot into OVMF and try manually loading the .efi (Boot
Hi Am Di., 29. Okt. 2019 um 14:02 Uhr schrieb Strahil <hunter86_bg@yahoo.com>: maintenance manager -> Boot from file) no disc is detected inside the CD-ROM, the list is empty. I'm guessing that I may have wrongly understood, hence wrongly configured certain options? Anyway, it would be interesting to compare the VM settings with my non-working case. I've attempted all possible combinations possible BIOS types and emulated machine type out of: - BIOS Type: Q35 Chipset with SecureBoot / Q35 Chipset with UEFI BIOS - Custom emulated machine: q35 / pc-q35-rhel7.6.0 What have been your settings that are known to work in your case? I may have made a stupid oversight at some point. Regards Mathieu
What exactly is your problem? In all cases booting the VM with a Windows boot disc no disc is detected, variants are shown When I boot into OVMF and try manually loading the .efi (Boot
Sadly, I can't check them any more - they are deleted, but I think that I got only the chipset changed. Have you tried with another ISO ? Best Regards,Strahil Nikolov В четвъртък, 31 октомври 2019 г., 13:54:23 ч. Гринуич+2, Mathieu Simon <mathieu.simon@gymneufeld.ch> написа: Hi Am Di., 29. Okt. 2019 um 14:02 Uhr schrieb Strahil <hunter86_bg@yahoo.com>: maintenance manager -> Boot from file) no disc is detected inside the CD-ROM, the list is empty. I'm guessing that I may have wrongly understood, hence wrongly configured certain options? Anyway, it would be interesting to compare the VM settings with my non-working case. I've attempted all possible combinations possible BIOS types and emulated machine type out of: - BIOS Type: Q35 Chipset with SecureBoot / Q35 Chipset with UEFI BIOS - Custom emulated machine: q35 / pc-q35-rhel7.6.0 What have been your settings that are known to work in your case? I may have made a stupid oversight at some point. Regards Mathieu _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KGIOHRHH2YEXGS...
Hi Am Sa., 2. Nov. 2019 um 08:51 Uhr schrieb Strahil Nikolov <hunter86_bg@yahoo.com>:
Have you tried with another ISO ? This is quite weird, still better than my initial testing but here it goes. I've slimmed down my attempts to Q35 and UEFI (both on and off):
- Server 2019 ISO boots into installer with or without SecureBoot enabled (I clearly remember it didn't work in any combination I've tried, but now it did, anyhow). The OS installes and boots with SecureBoot enabled - Server 2016 ISO fails to boot right at the windows bootloader*, however I don't care for Server 2016 that much anymore at that point in time, and it could well be that the ISO image could be of an older revision (MS does release updated images from time to time) - Debian 10 boots of the CD, however it doesn't seem like NVRAM changes are saved in oVirt / RHV guests yet. So at boot the OS doesn't start and you have to once boot from file (EFI disk -> EFI -> debian -> shimx64.efi) After the boot you you have to copy all (or only shimx64.efi?) to /boot/efi/EFI/BOOT as BOOTX64.EFI like Windows. Debian 10 has a Microsoft-signed shim loader so SecureBoot actually works. - Ubuntu 18.04 boots of the disc, installs and boots since their installer puts a copy of shimx64.efi into /boot/efi/EFI/BOOT which is where OVMF looks for a loader I'm I correctly guessing based on looking at the "VM devices" list per VM that oVirt/RHV doesn't yet provide a way to provide a persistent NVRAM image to guests? Sso for the time being we're actually stuck on Linux systems to have a EFI/BOOT/BOOTX64.EFI present? Is this the issue you wrote about? (I've encountered this very same issue on plain KVM and Proxmox, in both cases a small disk image is required per VM to make the content of the NVRAM persistent across VM reboots) Regards Mathieu * See screenshot uploaded here: https://imgur.com/a/ZsnbCOM
participants (3)
-
Mathieu Simon -
Strahil -
Strahil Nikolov