[SOLVED] Guest with encrypted passthrough Physical Disk to Virtual Machine not booting

M01vdTbxc

New Member
Jan 27, 2024
2
0
1
Hello

I have Linux installed on NVMe SSD with encrypted boot: https://wiki.archlinux.org/title/dm...entire_system#Encrypted_boot_partition_(GRUB)

I can unlock and boot the os without Proxmox without problems.

I have added the nvme drive to Linux guest with following config:

Code:
boot: order=scsi2
cores: 4
cpu: x86-64-v2-AES
efidisk0: local-lvm:vm-100-disk-1,efitype=4m,size=4M
memory: 8192
meta: creation-qemu=8.1.2,ctime=1706203363
name: march
net0: virtio=BC:24:11:00:B6:98,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi2: /dev/disk/by-id/nvme-Samsung_SSD_970_EVO_Plus_1TB_S4EWNX0NA77773A,backup=0,size=976762584K
scsihw: virtio-scsi-pci
smbios1: uuid=7eada97f-d105-4e81-ab3b-05eb0508f191
sockets: 1
unused0: local-lvm:vm-100-disk-0
usb0: host=046d:c33f
vga: virtio

I can run grub from EFI shell and it will ask for password for the boot partition and unlock it:
1706355071519.png

On Grub shell I can see that boot is unlocked and I can also see the keyfile. Grub boot entry options are:
1706355176663.png

But when trying to boot it seems like it fails to unlock other partitions and drops into emergency shell.


Is there any option I am missing on the Proxmox side?

Thank you for any help.
 
Last edited:
Hello again.

I got it to boot using initramfs-linux-fallback.img so it seems like i need to include some kernel module to initramfs image.
the encryption didn't have anything to do with the problem.
I will edit this message when I find the correct module.

Edit: I added:
Code:
virtio_net
virtio_console
virtio_balloon
virtio_scsi
virtio_pci

And now the desktop os is booting correctly as virtual machine
 
Last edited: