Hudratronium commented on issue #4238: URL: https://github.com/apache/cloudstack/issues/4238#issuecomment-1218556110
> I think the creation depends on whether the hypervisor supports it; for ex. if the platform is arm64, all VMs are UEFI based only; is this still a bug @gaaray2k ? Would this work for CS in a mixed environment (meaning UEFI capable and not capable hosts )? Up till now my understanding of the design reference ( https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enable+UEFI+booting+for+Instance ) is that UEFI is optional. Meaning even if a plattform (host) supports UEFI, the current standard for deployments still is BIOS (especially regarding the SystemVMs). @slavkap > But found that during migration with both cases - `migrateVirtualMachineWithVolume` and `migrateVirtualMachine` the `/var/lib/libvirt/qemu/nvram/[VM-UUID].fd` file is copied to the new host, but still exists and on the old one. Which I think has to be deleted I've seen that for the last releases (4.17) there have been some changes regarding the UEFI capabilies out of the box - do you know if this was "fixed" ? Also you wrote the link to the source for the content of the "uefi.properties"-file. Do you know if there have been some changes regarding the contents as well as of the deployment (kind of "inital" configuration) which might be deployed with 4.17? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
