Chris Adams linux@cmadams.net writes:
Once upon a time, Jared Dominguez jaredz@redhat.com 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)
Support tickets don't worry me as much as making breaking changes for customers that possibly result in outages for them do.
For example, I don't think it'd ever be possible to flip the default for existing EC2 instance types. Maybe the default for a new major OS version, but there's likely going to be an amount of time before all EC2 instance types support UEFI, and then there'll be customers with a multitude of custom things enabled that don't (at least yet) work with UEFI and will take the easy option of going back to legacy-bios, probably for years.