Stupid question: does the hypervisor need to be running in EFI mode as well for this to work properly?
I don't think that's a requirement at all, but just making sure. I am avoiding EFI like the plague, but at some point I'll need to bite the bullet. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Nathan Johnson" <njohn...@ena.com.INVALID> > To: "dev" <dev@cloudstack.apache.org> > Sent: Wednesday, 13 March, 2019 14:29:29 > Subject: Proposal for EFI firmware support on KVM > I've put together an approach for EFI support that we would like to get some > feedback on before I create a PR. Constructive criticism would be > appreciated. > > I've added the following properties to be configured in the agent.properties: > > guest.loader.efi - boolean to switch efi on. This must be true before it will > inject any <loader> entries into the domain xml > guest.loader.image - this would be the path to the bios/efi image > guest.loader.nvram - this optionally points to an nvram image > > > Even when a host is configured so that it can use EFI, it will only actually > create a virtual machine when both of the following conditions are met: > > 1) the host has guest.locader.efi set to true in its agent.properties > 2) the vm has the vm details parameter efi=true > > At present there is no automatic way for the management server to know in > advance which hosts have EFI enabled. I suppose this could be approximated > using tags. It might be nice to make this more automatic, and have the > resource planner aware of the efi toggle on the VM, but I'm not sure how best > to implement that or if it's even worth it. > > Thanks in advance! > > > Nathan Johnson > Senior R&D Engineer > Education Networks of America
