[SOLVED] Proxmox Update to 9.1.1 from 8.0 / VMs (Homeassistant) not starting

C

chey

New Member
Nov 27, 2025
7
1
3
Hi community,

i just updated the proxmox VE to latest 9.1.1.
Since then my VM, which includes my homeassistant OS, is not starting anymore.
I got stuck in grub (all slots and rescue shells resulting in crash/restart of VM).

I have backups from the VM and already restored one into a new VM, but went into the same problem.

Any ideas?

Thanks!
 
Sounds like the drive referenced in the VM definition has changed or is somehow unavailable.
Or boot order changed (a restore to a new VM could just put the same settings back in there).
could be more basic than you think

also look for warnings or errors down in the bottom pane. you may have that minimized.
 
Last edited:
Please share pictures of the boot progress as well as these
Bash: 
cat /etc/pve/storage.cfg
lsblk -o+FSTYPE,LABEL,MODEL
qm config VMIDOFHAOSHERE
 
Hi, attached the pictures of the "boot loop" and the outputs of the commands.
No errors in the bottom panel... Nor any error messages in the console- just the rebooting.
 

Attachments

Last edited:
Other than the lack of a Guest Agent (needed for proper backups) the configs look okay.
Can you select Slot A, press e, add the debug kernel argument and record the boot process with that?
 
Last edited:
Nothing happening with "debug" param other than "booting a command list" and then restarting. No log again.
To which path is the debug written?
 

Attachments

  • bootingcommandlist.png
    bootingcommandlist.png
    1.5 KB · Views: 2
To the screen. It's a temporary kernel argument to print more information.
I just noticed you didn't set a CPU so this will be somewhat slow. Try to set it to host. I'd also recommend to enable the start at boot and set localtime to default. You can also try to recreate the EFI disk but I'm grasping at straws at the moment.
 
Last edited:
CPU, StartAtBoot set and localtime disabled.
But still no output with debug option, other than last picture.
I feel something is broken with grub? I remember when preparing the upgrade it was recommended by pve8to9I to install grub-efi-amd64 which i did.
Maybe this was not good? :(
 
That shouldn't affect the VM though. Unfortunately I don't have many other ideas at this time.
 
Last edited:
@Impact,

Agreed, the host GRUB package change is unrelated to the VM's internal boot issue.

Since this is HAOS, two likely culprits after a major QEMU bump (PVE 9 uses QEMU 10.x):
  1. Machine Version: The update might have defaulted the VM to a newer Machine Type (e.g., pc-q35-9.1) which can have regressions. Try pinning it back to an older version like pc-q35-8.1 in the Hardware settings.
  2. Secure Boot: Ensure Secure Boot is explicitly disabled in the OVMF (UEFI) settings, as HAOS can be picky and defaults might have shifted.
 
Hi,
Secure boot is disabled when checking the VM.

I just saw, that the machine setting was "Default (i440fx)".
WIth setting to "q35" (any version) the result after startup is, that the console just shows "Guest has not initialized the display (yet)".

Many thanks so far!
 
Hi, this topic can be closed now.
I reinstalled the whole proxmox VE and made a restore of my VM and containers.
Everything works now as expected again.

Thank you for your help and ideas!
 
  • Like
Reactions: Impact
You must log in or register to reply here.
Top Bottom