No bootable option or device was found when booting qcow2 cloud image

avojak

New Member
Jan 28, 2026
4
0
1
avojak.com
Hello, I recently installed Proxmox VE 9.1.4 on a 2012 Mac mini and have been trying to deploy a new VM based on a qcow2 cloud image. I've mainly been trying to use the latest CentOS Stream 10 image, but have also tried others, including Ubuntu Server 24.04.

In each case, I have downloaded the qcow2 image into local storage from the import view:
Screenshot 2026-01-29 at 8.22.56 AM.png

The configuration that I'm most convinced should be correct is:

Code:
agent: 1
bios: ovmf
boot: order=scsi0;ide2;net0
cores: 4
cpu: x86-64-v2-AES
efidisk0: local-lvm:vm-102-disk-0,efitype=4m,size=4M
ide2: none,media=cdrom
machine: q35
memory: 8192
meta: creation-qemu=10.1.2,ctime=1769699803
name: test
net0: virtio=BC:24:11:BA:DD:2D,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local-lvm:vm-102-disk-1,discard=on,iothread=1,size=10G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=c822c3ed-1b74-4cd3-a673-558c42e7ce77
sockets: 1
vmgenid: c74cbff6-b454-4439-8c6c-aa7eef67cf41

Each time I try to boot the image, I'm greeted with the same message:

Failed to load Boot0002 "UEIF QEMU QEMU HARDDISK " from PciRoot (0x0)/Pci(0x1E,0x0)/Pci(0x4,0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0) : Not Found
No bootable option or device was found

Screenshot 2026-01-29 at 8.17.34 AM.png

In my research, I've found that the most common problem usually is that secure boot is enabled, but it is not:

Screenshot 2026-01-29 at 8.18.24 AM.png

I also tried following advice from this Wiki to modify UEFI boot entries, but I don't see anything in the file explorer:

Screenshot 2026-01-29 at 8.18.01 AM.png

I also tried manually importing the qcow2 image per the advice here: https://forum.proxmox.com/threads/f...age-disk-uefi-access-denied.99892/post-832900

I've also tried what feels like every combination of the configuration options for SCSI controller, disk device type, machine type, boot order, processor type, etc. etc.

I also tried using the default SeaBIOS type but that put the VM into a boot loop showing the Proxmox splash screen and the screen to pick the device to boot.

I was also able to reproduce the same issue on a different (also newly installed) Proxmox host on an Asus motherboard, so pretty different host hardware.

Any suggestion would be appreciated, I'm pretty stumped here!
 
Your images are imported/stored in your local storage but your VM uses local-lvm.
What process are you using here to "create" the image on local-lvm?
 
I did discover late yesterday night that I was in fact using the "wrong" qcow2 image. Apparently there are two (very similarly named) cloud images for CentOS Stream on x86_64, one just has an extra x86_64 in the name, and it supports EFI booting. (see: https://bugs.launchpad.net/kayobe/+bug/2121588)

After using the correct image I'm now stuck with the following screen:
1769805021670.png
Again, I've tried tweaking a few settings, but to no avail...

Looks to be the same issue mentioned before:
- https://forum.proxmox.com/threads/p...boot-option-message-when-i-start-a-vm.129170/
- https://forum.proxmox.com/threads/stuck-at-efi-boot-during-reboot-of-vm.123870/