'No bootable option or device was found' on new Windows VM.

[dwade]

I was able to create the first Windows VM fine.

I then tried to create a second Windows VM using the same iso file from the first VM, but it keeps getting the error below -


I have crossed reference the configurations from my first VM created, and everything is the same so am not sure what went wrong.

Below are the configurations of the second VM -



Any ideas?

 

[gfngfn256]

but it keeps getting the error below

I'm guessing that you press a key but it still refuses to boot into the Windows installation CD (ide2)?
Firstly maybe try setting that ide2 as the first (or only) in the boot order - till you finish the installation.
That ISO may have become corrupted. To test the ISO - on the original VM (working one) can you boot into the same CD?
Maybe download that Windows installation ISO again from Microsoft & check the provided checksum.

I have crossed reference the configurations from my first VM created, and everything is the same so am not sure what went wrong.

How long ago did you create the first VM?
Could you provide a full output of qm config <VMID> of both VMs (working & not) so that we can fully compare.

 

[dwade]

Maybe download that Windows installation ISO again from Microsoft & check the provided checksum.

Just tried downloading the ISO again and installed on a brand new VM, but still same issue.
I also tried setting ide2 as the only boot order, but no luck either.

How long ago did you create the first VM?
Could you provide a full output of qm config <VMID> of both VMs (working & not) so that we can fully compare.

The first VM was created a couple of days ago.

Here is the full output of the first VM (working):
agent: 1
bios: ovmf
boot: order=ide0;net0;ide1
cores: 4
cpu: host
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-100-disk-1,cache=writeback,discard=on,size=64G
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1737198604
name: HJT-MANAGE
net0: e1000=BC:24:11:E6:04:57,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=b5b7f077-5cdb-4f9c-9b02-2092d610130b
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
vcpus: 4
vmgenid: eab3eea1-dc5a-4907-9974-74b3270e58bb

Here is the second VM (not working):
agent: 1
bios: ovmf
boot: order=ide2
cores: 2
cpu: host
efidisk0: local-lvm:vm-200-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-200-disk-1,cache=writeback,discard=on,size=64G
ide2: local:iso/Win11_24H2_EnglishInternational_x64.iso,media=cdrom,size=5695402K
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1737370785
name: HJT-RDS
net0: e1000=BC:24:11:CA:53:E9,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=69b8b99d-bf4c-4342-bd33-4a4bb23d22a3
sockets: 1
tpmstate0: local-lvm:vm-200-disk-2,size=4M,version=v2.0
vmgenid: 2a8df8d0-0b1c-4fb8-b70b-6b0deca60fdd

One thing noted is that when I change the BIOS from OVMF to SeaBIOS, then the VM is able to boot up the ISO image.

 

[gfngfn256]

You have not covered everything I asked:

I'm guessing that you press a key but it still refuses to boot into the Windows installation CD (ide2)?

Can you press a key to enter the Boot Manager Menu - as is displayed in your boot-screen image ?

How much space do you have on that local-lvm ?

 

[dwade]

Can you press a key to enter the Boot Manager Menu - as is displayed in your boot-screen image ?

The attached is what is shown. I tried to select the hard disk, but nothing happens.

Below is the current usage of the local-lvm:
12.58% (19.08 GB of 151.64 GB)

 

[gfngfn256]

I tried to select the hard disk, but nothing happens.

You then have to save & exit. But it won't boot from that QEMU HD at this point as the HD is blank as you have not as yet installed Windows.
You should be trying to boot from the CD (Windows Installation not the VirtIO drivers one).

From that vBIOS screen - can you select Device Manager & then Secure Boot Configuration & then turn off Attempt Secure Boot. F10 to save & Exit.

 

[gfngfn256]

I just wanted to point out one difference I noted between your 2 VM's configs - is the number of cores you are using. In the working one you have 4 - in the non-working one you have 2. I would be surprised if this was stopping the ISO installation from booting - but you never know. (I looked it up & technically you can upgrade from Windows 10 to 11 with 2 cores, but cannot find info. on a clean Windows 11 install if it can be done on a 2 core PC).

 

[dwade]

You then have to save & exit. But it won't boot from that QEMU HD at this point as the HD is blank as you have not as yet installed Windows.
You should be trying to boot from the CD (Windows Installation not the VirtIO drivers one).

From that vBIOS screen - can you select Device Manager & then Secure Boot Configuration & then turn off Attempt Secure Boot. F10 to save & Exit.

I have previously attempted to boot from the CD but no luck either.

I have also tried tinkering with Secure Boot and disabled this but still no dice.

As for the number of cores, I have also tried increasing to 4, but since it still didn't work, I reverted it back to 2.

While I could get it to boot up in SeaBIOS, I couldn't actually install Windows 11 as it said the computer did not meet the minimum requirements, even though it is the same specs as the working VM (this is after I increased to 4 cores).

 

[dwade]

Update: I manage to get this working after changing the Hard disk from IDE to SATA.

Strange it worked on the first VM even though the disk was set to IDE.

 

[gfngfn256]

Strange it worked on the first VM even though the disk was set to IDE.

Indeed. Possibly it has something to do with the number of IDE devices being used. I remember reading once users having trouble booting in UEFI with multiple/numerous IDE devices. If I have a chance I'll try replicating your setup & testing.

 

[gfngfn256]

OK just installed - replicating your exact setup - 20 minutes fully installed - Fully working & Updated.
Here is my config:

# qm config 106
agent: 1
bios: ovmf
boot: order=ide1;ide0;ide2;net0
cores: 4
cpu: host
efidisk0: Storage:106/vm-106-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: Storage:iso/virtio-win.iso,media=cdrom,size=707456K
ide1: Storage:106/vm-106-disk-1.qcow2,cache=writeback,discard=on,size=64G
ide2: Storage:iso/Win11_24H2_EnglishInternational_x64.iso,media=cdrom,size=5695402K
machine: pc-q35-9.0
memory: 8192
meta: creation-qemu=9.0.2,ctime=1737441895
name: Windows11
net0: e1000=BC:24:11:C9:67:60,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=e14ea1c9-8d3e-401e-ad08-1901a9469626
sockets: 1
tpmstate0: Storage:106/vm-106-disk-2.raw,size=4M,version=v2.0
vmgenid: 24fd3db8-398f-445d-8641-2fe9b9c69ca0