-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting BIOS VM in Arch Linux - Error: Couldn't find one of the required UEFI firmware files: [] #1572
Comments
The ArchLinux package directly sets
|
Thanks for your quick response @stgraber . |
Our firmware detection logic evolved quite a bit over time. But given that it appears to find them all just fine now, the env variable should go away. |
Thank you! |
Required information
Issue description
I try to launch a BIOS-mode VM with Incus, using
security.csm=true
andsecurity.secureboot=false
.When starting the VM, I get the following error:
Full output of
incus info --show-log trinity-poc
is the following:This was first discussed in the following Linux containers forum post:
https://discuss.linuxcontainers.org/t/attempting-to-launch-a-vm-fails-looking-for-empty-list-of-uefi-firmwares/22365/3
Steps to reproduce
9.1.2-1
because of incus storage volume attach prevents startup of VM for some (longer than 14 characters?) storage names with qemu 9.1.1 #1536 , please see my comment on that bug for more information.incus storage volume import default \ ~/debian-12.8.0-amd64-netinst.iso \ debian-iso-volume \ --type=iso incus init trinity-poc \ --empty \ --vm \ -c limits.cpu=4 \ -c limits.memory=8GiB \ -c security.csm=true \ -c security.secureboot=false \ --profile default \ --profile vlan_servers incus config device add trinity-poc iso-volume disk \ pool=default \ source=debian-iso-volume \ boot.priority=10 incus start trinity-poc
Information to attach
dmesg
): Nothing is written to dmesg during this errorincus info NAME --show-log
): Attachedincus config show NAME --expanded
): Aboveincus monitor --pretty
while reproducing the issue): Attachedincus-monitor-pretty.txt
incus-debug-start.txt
incusd.log
incus-config-show-expanded.txt
The text was updated successfully, but these errors were encountered: