Almalinux 9.6 - UEFI Secure/Legacy Boot

[wverleger]

Hi,

using: ACS 4.19.3.0
Hypervisor: Alma Linux 9.6
Instance: Ubuntu 24 LTS

I was wondering if there is any limitation with Alma Linux 9.6 and UEFI Secure/Legacy Boot?

Trying to create/start a VM results in a error message:

UI
Unable to start a VM [0ac37123-6419-4987-92f8-313077c988c6] due to [Unable to create a deployment for VM instance {"id":1196,"instanceName":"i-50-1196-VM","state":"Starting","type":"User","uuid":"0ac37123-6419-4987-92f8-313077c988c6"}].

MGMT Logs

2025-08-19 15:39:00,366 ERROR [c.c.v.VmWorkJobDispatcher] (Work-Job-Executor-115:ctx-988407c7 job-48552/job-48554) (logid:2bb20fa8) Unable to complete AsyncJobVO: {id:48554, userId: 102, accountId: 50, instanceType: null, instanceId: null, cmd: com.cloud.vm.VmWorkStart, cmdInfo: rO0ABXNyABhjb20uY2xvdWQudm0uVm1Xb3JrU3RhcnR9cMGsvxz73gIAC0oABGRjSWRMAAZhdm9pZHN0ADBMY29tL2Nsb3VkL2RlcGxveS9EZXBsb3ltZW50UGxhbm5lciRFeGNsdWRlTGlzdDtMAAljbHVzdGVySWR0ABBMamF2YS9sYW5nL0xvbmc7TAAGaG9zdElkcQB-AAJMAAtqb3VybmFsTmFtZXQAEkxqYXZhL2xhbmcvU3RyaW5nO0wAEXBoeXNpY2FsTmV0d29ya0lkcQB-AAJMAAdwbGFubmVycQB-AANMAAVwb2RJZHEAfgACTAAGcG9vbElkcQB-AAJMAAlyYXdQYXJhbXN0AA9MamF2YS91dGlsL01hcDtMAA1yZXNlcnZhdGlvbklkcQB-AAN4cgATY29tLmNsb3VkLnZtLlZtV29ya5-ZtlbwJWdrAgAESgAJYWNjb3VudElkSgAGdXNlcklkSgAEdm1JZEwAC2hhbmRsZXJOYW1lcQB-AAN4cAAAAAAAAAAyAAAAAAAAAGYAAAAAAAAErHQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAHBwcHBwcHBwc3IAEWphdmEudXRpbC5IYXNoTWFwBQfawcMWYNEDAAJGAApsb2FkRmFjdG9ySQAJdGhyZXNob2xkeHA_QAAAAAAADHcIAAAAEAAAAAR0AApWbVBhc3N3b3JkdAAfck8wQUJYUUFFRGhTWkZOWFJEUkNabGgzVTFwUVpuZ3QACEJvb3RNb2RldAASck8wQUJYUUFCbE5GUTFWU1JRdAAIQm9vdFR5cGV0AA9yTzBBQlhRQUJGVkZSa2t0AAhVZWZpRmxhZ3QADnJPMEFCWFFBQTFsbGN3eHA, cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result: null, initMsid: 165989263229575, completeMsid: null, lastUpdated: null, lastPolled: null, created: Tue Aug 19 15:38:47 CEST 2025, removed: null}, job origin:48552 com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM instance {"id":1196,"instanceName":"i-50-1196-VM","state":"Starting","type":"User","uuid":"0ac37123-6419-4987-92f8-313077c988c6"}Scope=interface com.cloud.dc.DataCenter; id=1 at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1239) at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:5496) at jdk.internal.reflect.GeneratedMethodAccessor994.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:105) at com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5620) at com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:654) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102) at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45) at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:602) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)

cs_logs.txt

(more logs attached)

Hosts support UEFI:

Cloudstack Agent settings:

guest.nvram.template.secure=/usr/share/OVMF/OVMF_VARS_4M.ms.fd
guest.nvram.template.legacy=/usr/share/OVMF/OVMF_VARS_4M.fd
guest.nvram.path=/var/lib/libvirt/qemu/nvram/
guest.loader.secure=/usr/share/OVMF/OVMF_CODE_4M.secboot.fd
guest.loader.legacy=/usr/share/OVMF/OVMF_CODE_4M.fd

The same setup using Ubuntu 24 LTS as hypervisors works out of the box.

[weizhouapache]

it seems to be related the to affinity group with type ExplicitDedication

[wverleger]

I was able to fix it. I had a mix up in the uefi.properties settings for Alma Linux.
Corrected settings are:

guest.nvram.template.secure=/usr/share/edk2/ovmf/OVMF_VARS.secboot.fd
guest.nvram.template.legacy=/usr/share/edk2/ovmf/OVMF_VARS.fd
guest.loader.secure=/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd
guest.loader.legacy=/usr/share/edk2/ovmf/OVMF_CODE.fd
guest.nvram.path=/var/lib/libvirt/qemu/nvram/