GitHub user winterhazel added a comment to the discussion: Starting instances in a domain other than root fails,
> Enabling the uefi.properties what does it really do? Do i need it? It is the > only way for a tenant (subdomain) admin or user to start uefi secure or > insecure VMs? Yes, this is needed. This file tells CloudStack where the UEFI firmware is located at, so that it can create VMs using that firmware. > -Cannot find how to change to bios. Only options available are name, display > name, os type, dynamically scalable, ha enabled, group, delete protection. > Plus a few under instance settings. (like UEFI secure or legacy). Under instance settings, delete the `UEFI` setting. The VM will boot using BIOS when this setting is not defined. > All my VMs and templates are based on ubuntu20-22, debian12, windows 2022, > all using uefi secure. Nowhere bios except for the system VM template > (centos5.5). > After enabling the uefi-properties file and restarting the agent, some old > centos system template based VM starts fine. All the VMs I created based on > my iso and templates either cannot start or start but cannot boot. > I am asking because all my uefi instances worked fine prior to enabling it. Your VMs were booting using BIOS (not UEFI) before creating the `uefi.properties`. Even if there is the `UEFI` setting under their instance settings, CloudStack configures existing VMs to boot using BIOS instead of UEFI if no `uefi.properties` is found in a host. I assume that your templates were created from MBR disks with BIOS-compatible bootloaders because you were using BIOS when installing the OS. Therefore, now that the VMs are actually using UEFI, they cannot boot because there is no EFI partition with a bootloader. Could you configure the VMs to boot using BIOS, as described above, and check whether they start successfully? > (help! how can i delete old templates? no delete button...) You can delete a template by accessing its details page and going to the zones tab. There will be a button to delete the template from each zone that it is installed in. > Also do you think I need a uefi storage pool as defined for Alma while i am > running rhel8? > (https://www.siberoloji.com/set-uefi-boot-kvm-virtual-machines-almalinux/) You don't need to create this pool. GitHub link: https://github.com/apache/cloudstack/discussions/10430#discussioncomment-12468562 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
