Is It possible to boot directly from a NVMe that is passed-through ?

[inDane]

Hi fellas,
im using OVMF (UEFI) and id like to boot directly from a NVMe drive, which is passed-though.

it basicly works, but not automatically. I don't know where to change it. If i change anything in the boot menu of EFI, it will "forget" it at next boot of the VM.
I can manually boot it via EFI shell or via Boot Menu, but how can I automate it?

Best
inDane

 

[wolfgang]

Hi,

no this is not supported at the moment.
But you can make a feature request at bugzilla.proxmox.com

 

[inDane]

Hi,
I accidentally found a workaround.
Usually there is a regular disk created with the VM. The default size for a Win10 VM is 32GB. Delete/Detach this disk. Boot the machine, go into the EFI settings, change the boot order again and voilá, it works.

Best regards
inDane

 

[AngryAdm]

This was pointed out two years ago. Someone of the proxmox staff "didnt have a spare nvme" lying around at that time.
About time this gets fixed...

I would not consider it a "feature request" since the feature is already in the bios to select the passed through nvme. The bios just resets the settings which is more like bug than a missing feature.

https://forum.proxmox.com/threads/cannot-edit-boot-order-with-nvme-drive.49179/

 

[AngryAdm]

Hi fellas,
im using OVMF (UEFI) and id like to boot directly from a NVMe drive, which is passed-though.

it basicly works, but not automatically. I don't know where to change it. If i change anything in the boot menu of EFI, it will "forget" it at next boot of the VM.
I can manually boot it via EFI shell or via Boot Menu, but how can I automate it?

Best
inDane

What you have to do to make it work is the following:
1. in web gui under options, change the boot order so that 1. is scsi0 then remove cd-rom and network.
2. go to your hardware section in the web gui and remove the EFI disk if any.
3. edit your configuration file in /etc/pve/qemu-server/XXX.conf and change any scsi0 device to be scsi1.
That essentially makes the boot order you changed in 0 invalid as there is no scsi0 disk to boot and somehow it boots the nvme.

That way I got it working after fiddling around for several days.