uefi vm creation fail

[gaaray2k]

ISSUE TYPE

• Bug Report

COMPONENT NAME

CLOUDSTACK VERSION

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

VM creation fails when creting a vm with uefi bios

STEPS TO REPRODUCE

create an instance with a uefi bios

EXPECTED RESULTS

vm is created sucessfully

ACTUAL RESULTS

2020-06-23 11:44:19,025 ERROR [kvm.resource.LibvirtComputingResource] (main:null) (logid:) uefi properties file not found due to: Unable to find file uefi.properties.

[gaaray2k]

from https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enable+UEFI+booting+for+Instance it says:

In case of newly configuring KVM Host , Cloud Admin [Customer admin] will have to prepare and add uefi.properties after successful completion of agent.

is this a file I need to create manually? If so, how?

[DaanHoogland]

@gaaray2k I have never tested UEFI with any thing but vmware and I thought on KVM firmware emulation does not apply as all properties are set in the spec xml that qemu uses. However reading that page it says an extra package needs to be installed on KVM to support UEFI.

{ eg: KVM host additional OVMF package is required to boot Guest VM in UEFI mode}
Did you do that?
As i don't know of any other users atm I think you are on your own. Try addressing the author of the feature.

[DaanHoogland]

@gaaray2k can you test this with 4.15, please?

[DaanHoogland]

@gaaray2k did you find an answer and can you share it?

[slavkap]

I'm not @gaaray2k but I could tell how I did the setup on one of my hosts. My configuration is according to the steps from PR #3638

I have installed OVMF and have created uefi.properties with those details

and in /etc/libvirt/qemu.conf file I have added
nvram = ["/usr/share/OVMF/OVMF_CODE.secboot.fd:/usr/share/OVMF/OVMF_VARS.fd"]

Because my host wasn't newly created I have changed in host_details table the value for "host.uefi.enable" of the respective host to true. I have tested it also by adding a new host.

I couldn't find a qcow2 image with EFI to test deploying a VM from a template, but deploying a VM with ISO works, but at runtime, I've replaced the bus from 'ide' to 'sata'

[DaanHoogland]

@slavkap , that sounds like the adding of uefi.properties should be part of the agent setup/host connect procedure, should it?
cc @weizhouapache @wido @pavanaravapalli ?

[slavkap]

@DaanHoogland , I think that for the end-user it will be ok the uefi.properties file to be included. But I don't have experience in this, because for the last three days I'm "playing" with this feature :) So somebody else has to say which option is better

[Hudratronium]

@slavkap , that sounds like the adding of uefi.properties should be part of the agent setup/host connect procedure, should it? cc @weizhouapache @wido @pavanaravapalli ?

+1

I would really appreciate this, as the managementserver GUI will show this option even if no uefi-capable hosts for instance deployment are availeable.
So from a users point of view, uefi-boot is availeable all of the time.
Another topic might be to dispaly some more informations in the advanced - mode menue as, according to https://cwiki.apache.org/confluence/display/CLOUDSTACK/Enable+UEFI+booting+for+Instance there are some limitations.
"Guest VM which is deployed in UEFI mode , restricted to migrate another Host[with UEFI capability]"

@slavkap
Did you have issues migrating uefi-secureboot instances between different hosts?

[slavkap]

@Hudratronium, I don't remember. I will test and let you know

[Hudratronium]

That would be really appreaciated.
Currently the docs as well as the wiki are quiet ... empty regarding this whole topic.

[slavkap]

@Hudratronium, I did some tests with the migration. It works on stopped VMs (tested with NFS/StorPool), few scenarios with live migration (migrateVirtualMachineWithVolume):

hypervisor KVM
NFS storage pool Zone-wide:

• failed to migrate to another NFS with zone-wide scope
• success while migrating to NFS storage with cluster-wide scope

StorPool storage pool Zone-wide:

• success in migrating to another host and different StorPool storage pool