Once upon a time, Jared Dominguez <jaredz@xxxxxxxxxx> said: > Looks like they are using vSphere, which supports UEFI VMs. The same is > true for KVM, Xen and bhyve, so it's more about what feature set cloud > providers using these hypervisors are choosing to turn on. In a way, this is similar to "your router supports IPv6, why don't you just turn it on?": - version considerations: when did $HYPERVISOR start supporting UEFI? what versions may still be running in some parts of infrastructure? - "support" vs. "really support": just because something says it "supports UEFI" doesn't mean it works right; large-scale hosters need to do lots of testing of all their supported systems and setups to see how they actually react - internal tooling: just because a hoster is using KVM for example doesn't mean they just install the vendor software and go; they have their own internal management systems built on top, calling vendor APIs to do things - presentation: adding user-facing options should always be carefully considered, especially when they are "change this option and your VM possibly won't boot" type (so more support tickets) That all combines to lots of effort to support UEFI booting. When there's little demand, and little obvious gain up front, low-overhead providers aren't going to put that high on the priority list. -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
