Failing to boot Home Assistant qcow2 image disk - UEFI Access Denied

How does importing an existing QCOW disk work?
I created a VM, stored the QCOW home assisant disk on storage, and then manual renamed it to the disk name as created by the VM.
Or is there a fancier option which just allows you to select the disk via the Proxmox webgui?

Disabling 'Secure Boot' does not get my Home Assistant to work btw?
 
Last edited:
macamba said:
How does importing an existing QCOW disk work?
I created a VM, stored the QCOW home assisant disk on storage, and then manual renamed it to the disk name as created by the VM.
Or is there a fancier option which just allows you to select the disk via the Proxmox webgui?

Disabling 'Secure Boot' does not get my Home Assistant to work btw?
Click to expand...
I used this as a guide :
https://mangolassi.it/topic/21751/import-a-qcow2-into-proxmox

Worked for me once I changed from Seabios to UEFI bios.
 
Last edited:
salpot said:
Disabling Secure boot fixed my problem. I should have updated my post earlier, sorry.



Not in your host machine, but in the Proxmox VM. When you see the Proxmox logo when booting a VM, hit escape and then go to Device Manager -> Secure Boot Configuration then disable Attempt Secure Boot.
Click to expand...
Created an account just to thank you for this -- most appreciated! :))
 
salpot said:
Disabling Secure boot fixed my problem. I should have updated my post earlier, sorry.



Not in your host machine, but in the Proxmox VM. When you see the Proxmox logo when booting a VM, hit escape and then go to Device Manager -> Secure Boot Configuration then disable Attempt Secure Boot.
Click to expand...
wow, you saved me from jumping off the window :D thanks
 
TY; this was my issue as well

salpot said:
Disabling Secure boot fixed my problem. I should have updated my post earlier, sorry.



Not in your host machine, but in the Proxmox VM. When you see the Proxmox logo when booting a VM, hit escape and then go to Device Manager -> Secure Boot Configuration then disable Attempt Secure Boot.
Click to expand...
 
salpot said:
Disabling Secure boot fixed my problem. I should have updated my post earlier, sorry.



Not in your host machine, but in the Proxmox VM. When you see the Proxmox logo when booting a VM, hit escape and then go to Device Manager -> Secure Boot Configuration then disable Attempt Secure Boot.
Click to expand...

2025 is calling to say this is still the fix. Came here when failing to use OVMF as BIOS for VM's for GPU passthrough.
 
Last edited:
salpot said:
Disabling Secure boot fixed my problem. I should have updated my post earlier, sorry.



Not in your host machine, but in the Proxmox VM. When you see the Proxmox logo when booting a VM, hit escape and then go to Device Manager -> Secure Boot Configuration then disable Attempt Secure Boot.
Click to expand...
Another guy here who created the account just to say THANK YOU!!

May $Deity be pleased by your altruism to others.
 
Was running into this problem for a long time, could not figure it out for the life of me. Finally got it working! It wasn't about secure boot, preregistered keys, UEFI, disk controllers, etc.

The problem, for me, was silently happening in the qm disk import / qm importdisk step. This while reporting successful disk import. I don't know why, but it must have been choking on the HAOS partition table. This happened every one of the ~dozen times I tried it, and the biggest clue was that it would sometimes completely mangle the partition table, whereas other times it would just throw CPU faults on VM startup.

I wasn't catching those CPU faults at first, because from the main VM console, it looked like it was just hanging at boot. However, when I attached a serial device and connected the xterm.js console early enough during VM startup, I would see errors like this:

Code: 
BdsDxe: loading Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x5,0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0)
BdsDxe: starting Boot0002 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x5,0x0)/Pci(0x1,0x0)/Scsi(0x0,0x0)
!!!! X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 00000000 !!!!
ExceptionData - 0000000000000000
RIP  - 00000000BD9E7F5B, CS  - 0000000000000038, RFLAGS - 0000000000010286
RAX  - 00000000BD9FCD20, RCX - 000000000000000D, RDX - 0000000000000008
RBX  - A6FAF5EC4E2B04C6, RSP - 00000000BFE8B630, RBP - 00000000BFE8B650
RSI  - 0000000000000174, RDI - 00000000BD9EF4D2
R8   - 0000000000000002, R9  - 00000000BD9E11D8, R10 - 00000000BD9EAE38
R11  - 0000000000000000, R12 - 00000000BD9EF4D2, R13 - 00000000BD9E9B54
R14  - 0000000000000174, R15 - 0000000000000002
DS   - 0000000000000030, ES  - 0000000000000030, FS  - 0000000000000030
GS   - 0000000000000030, SS  - 0000000000000030
CR0  - 0000000080010033, CR2 - 0000000000000000, CR3 - 00000000BFC01000
CR4  - 0000000000000668, CR8 - 0000000000000000
DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 00000000BF9DB000 0000000000000047, LDTR - 0000000000000000
IDTR - 00000000BF202018 0000000000000FFF,   TR - 0000000000000000
FXSAVE_STATE - 00000000BFE8B290
!!!! Find image based on IP(0xBD9E7F5B) (No PDB)  (ImageBase=00000000BD9E1000, EntryPoint=00000000BD9E2000) !!!!

Other times, when qm disk import failed to copy the partition table at all (despite reporting success!), I would instead get output like this:

Code: 
BdsDxe: failed to load Boot0003 "UEFI QEMU QEMU HARDDISK " from PciRoot(0x0)/Pci(0x1E,0x0)/Pci(0x1,0x0)/Pci(0x5,0x0)/Scsi(0x0,0x0): Not Found

Solution​


Imaging the disk manually solved the problem:

Bash: 
wget <...>/haos_ova-<...>.qcow2.xz
unxz <file>.qcow2.xz
qemu-img info <file>.qcow2 # sanity check
qemu-img convert -f qcow2 -O raw <input>.qcow2 <output>.img
dd if=<file>.img of=<your vm disk> bs=4M status=progress conf=fsync
fdisk -l <your vm disk> # verify partition table

# for example:
wget https://github.com/home-assistant/operating-system/releases/download/17.0/haos_ova-17.0.qcow2.xz
unxz haos_ova-17.0.qcow2.xz
qemu-img info haos_ova-17.0.qcow2
qemu-img convert -f qcow2 -O raw haos_ova-17.0.qcow2 haos_ova-17.0.img
dd if=haos_ova-17.0.img of=/dev/mapper/StorageArray--vg-vm--105--disk--1 bs=4M status=progress conv=fsync
 
You must log in or register to reply here.
Top Bottom