Proxmox can't start boot VM - HassOS

[czarny1p]

Hi,
i have Virtual Environment 7.3-6
I update proxmox and reboot machin then VM can't start.



I wanted to run the bios menu but when i click ESC the screen just shows that and nothing happens


On VM was running HomeAssistant - HassOS

I don't know much about proxmox, could someone help me?

 

[Moayad]

Hello,

Can you post the output of pveversion -v and the VM config qm config <VMID>?

 

[czarny1p]

Hello,

Can you post the output of pveversion -v and the VM config qm config <VMID>?

Yes.

root@proxmox:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.85-1-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-6
pve-kernel-5.15: 7.3-2
pve-kernel-5.4: 6.4-20
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.4.203-1-pve: 5.4.203-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-6
libpve-storage-perl: 7.3-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.2-7
pve-firmware: 3.6-3
pve-ha-manager: 3.5.1
pve-i18n: 2.8-3
pve-qemu-kvm: 7.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1

qm config:

root@proxmox:~# qm config 100
agent: 1
balloon: 3072
bios: ovmf
boot: order=sata0
cores: 2
efidisk0: local-lvm:vm-100-disk-0,size=4M
hotplug: disk
memory: 3584
name: hassosova-4.20
net0: virtio=1A:6C:68:D4:2E:87,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
sata0: local-lvm:vm-100-disk-1,discard=on,size=90G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=c573f05d-5678-436d-a964-c4d0ba0b0955
sockets: 1
tablet: 0
usb0: host=5-1,usb3=1
vmgenid: a9d9c6b4-31fe-4272-a4e7-8a15241249e6

 

[Moayad]

Hi,

Can you try to b disable the secure boot of the VM?

 

[czarny1p]

Hi,

Can you try to b disable the secure boot of the VM?

I can't get into the menu.
When I press ESC the screen stays on the last screen

 

[czarny1p]

could anyone help/

 

[gruzdev]

I have the same problem
https://forum.proxmox.com/threads/homeassistant-booting-slot-a-ok-1-try-1.124289/

 

[fiona]

Hi,
just some guesses, but does it work if you select machine version 7.0 under Hardware > Machine > Edit > Version in the UI? Does downgrading QEMU or the OVMF firmware help, i.e. apt install pve-qemu-kvm=7.1.0-4 or apt install pve-edk2-firmware=3.20220526-1?

 

[gruzdev]

Hi,
just some guesses, but does it work if you select machine version 7.0 under Hardware > Machine > Edit > Version in the UI? Does downgrading QEMU or the OVMF firmware help, i.e. apt install pve-qemu-kvm=7.1.0-4 or apt install pve-edk2-firmware=3.20220526-1?

Yep.
After downgrading working.
apt install pve-edk2-firmware=3.20220526-1

 

[gruzdev]

Hi,
just some guesses, but does it work if you select machine version 7.0 under Hardware > Machine > Edit > Version in the UI? Does downgrading QEMU or the OVMF firmware help, i.e. apt install pve-qemu-kvm=7.1.0-4 or apt install pve-edk2-firmware=3.20220526-1?

Work for me.
After upgrade to 7.4, downgrading pve-edk2-firmware from 3.20221111-2 to 3.20220526-1 and reboot

 

[fiona]

usb0: host=5-1,usb3=1

What kind of device are you passing through? Does it work with the new pve-edk2-firmware package if you remove the passthrough? I haven't been able to reproduce the issue here yet unfortunately.

 

[MRobi]

Hi,
just some guesses, but does it work if you select machine version 7.0 under Hardware > Machine > Edit > Version in the UI? Does downgrading QEMU or the OVMF firmware help, i.e. apt install pve-qemu-kvm=7.1.0-4 or apt install pve-edk2-firmware=3.20220526-1?

Just upgraded to 7.4 today without having seen this. Now stuck with the same boot issue as above. Tried all of the suggested and still having the same issue.

Are there any other solutions to try with this?

 

[fiona]

Hi,

Just upgraded to 7.4 today without having seen this. Now stuck with the same boot issue as above. Tried all of the suggested and still having the same issue.

Are there any other solutions to try with this?

did you also try apt install pve-edk2-firmware=3.20220526-1? If that didn't help, it's likely a different issue. What CPU model does your host have? Please share the VM's configuration qm config <VMID>.

 

[MRobi]

Hi,

did you also try apt install pve-edk2-firmware=3.20220526-1? If that didn't help, it's likely a different issue. What CPU model does your host have? Please share the VM's configuration qm config <VMID>.

I did try that and it was still stuck in the same boot loop. However I did find the solution for me over on the Home Assistant forums. It involved changing the processor type of the VM from default to Host. After doing that it boots no problem.

Had a simular problem (the same sympthoms) after upgrading to proxmox 7.3 . Non of the VM-s started, they were stuck in a loop. Tried creating a new VM for HA with the same result.
I managet to solve the problem by setting the processor type of the virtual machines from the default to HOST. (Hardware>Processors - edit and set type to HOST the default i think was KVM or QEMU).
After setting all of my VM-s to this processor type all started again.

 

[fiona]

I did try that and it was still stuck in the same boot loop. However I did find the solution for me over on the Home Assistant forums. It involved changing the processor type of the VM from default to Host. After doing that it boots no problem.

Thank you for sharing the solution! What CPU model does your host have (can be seen with lscpu for example)?

 

[MRobi]

Thank you for sharing the solution! What CPU model does your host have (can be seen with lscpu for example)?

It's an i5-3450.

I also tried the VM on my other server which has dual Xeon E5-2690's before I found the above solution of setting the processor type.