PVE/Proxmox: Stuck in a boot-reset loop after adding kernel parameter
Posted: Wed May 22, 2024 9:08 pm
[PROBLEM]
After adding new kernel parameters for full IOMMU separation of hardware devices (See Proxmox PVE: passthrough of non-GPU + split IOMMUs).
Seems like loading the kernel module (?) for `pcie_acs_override` support, triggers to load the mokmanager.efi boot image:
By default, the "reset system" option seems to be selected, causing the system to get stuck in a boot-loop.
[SOLUTION]
It seems to be sufficient to "confirm" the change of boot-parameters, by selecting "always continue boot".
However, I'm personally a bit unsatisfied with this, as I don't yet fully understand what caused mokmanager to load in the first place, and if there's anything else that I *should* have done, rather than just saying "ignore and continue"?
Related proxmox forum entry:
https://forum.proxmox.com/threads/addin ... er.147538/
After adding new kernel parameters for full IOMMU separation of hardware devices (See Proxmox PVE: passthrough of non-GPU + split IOMMUs).
Seems like loading the kernel module (?) for `pcie_acs_override` support, triggers to load the mokmanager.efi boot image:
- proxmox_pve-mokmanager_boot_loop.jpg (11.1 KiB) Viewed 3463 times
[SOLUTION]
It seems to be sufficient to "confirm" the change of boot-parameters, by selecting "always continue boot".
However, I'm personally a bit unsatisfied with this, as I don't yet fully understand what caused mokmanager to load in the first place, and if there's anything else that I *should* have done, rather than just saying "ignore and continue"?
Related proxmox forum entry:
https://forum.proxmox.com/threads/addin ... er.147538/