pve 8.0 and 8.1 hangs on boot

[akulbe]

@Pakillo77 I'm not sure what changed, but I ended up installing again on the same server a few weeks later, and the issues I had initially no longer happened. I was frustrated like crazy, but it's working *great* now. Are you still seeing this issue?

 

[DXi]

I downloaded and installed 8.1 and got this same issue. I spent far longer than was reasonable trying all of the solutions, but didn't get anywhere. The older iso worked fine.

No amount of simplefb, nomodeset or bios options made any difference.

This was on a Optiplex 7050 SFF PC. Which I realize is not the intended hardware, but I was just poking around. It's all Intel chipsets and network inside.

 

[Pakillo77]

@Pakillo77 I'm not sure what changed, but I ended up installing again on the same server a few weeks later, and the issues I had initially no longer happened. I was frustrated like crazy, but it's working *great* now. Are you still seeing this issue?

Just updated BIOS, iDRAC and Proxmox on one of the Dell R240 and it boots up ok.
Let's see if it's stable in the next weeks.

Thanks,

 

[jasper702]

Hi guys, I found that if you disable x2APIC in BIOS under processor configuration it works fine with the new kernel. It seems that the problem is related with how the new kernel handles multi threading but because R240 is a one cpu server this option is not needed for me at least.

Thank you! This also resolved the issue for me on a Dell T140 that would not boot after a pve7to8 upgrade and reboot (new kernel).

 

[bysaRD]

3rd April 2024. Still same problem. This is not for production. I have removed GPU but onboard, used every possible type of install available. 7.4 - no problem, 8.1 unusable. I'm not sure how developers were able to miss this and more... how they are unable to solve it.

 

[t.lamprecht]

Still same problem.

If it's the same problem then the documented workaround that helped all having this exact problem in this thread will also help you.

If not I recommend opening an enterprise support ticket with Dell's and/or our support, as Dell's HW engineers have full access to their proprietary systems docs and can easily fix such stuff with sending patches to the kernel, and if it's a completely other issue our enterprise support might be able to help to identify what caused it with being able to take an actual closer look as per the subscription agreement.

 

[caelumtech]

I ran into similar issues on an old T420. Fresh install from 8.2 iso resulted in hard lock at loading initial ramdisk. After trying everything from this thread and others, I downloaded and installed the 7.4 iso, which went fine. I then changed the sources.list and the upgrade to bookworm was also successful. I'm not really interested in drilling down on why this works and a fresh install from 8.2 doesn't, but I thought I would share my experience.

 

[nordeep]

I have old HW:
8 x Intel(R) Xeon(R) CPU E5630 @ 2.53GHz (1 Socket) - 16GB
Intel S5500BC

Stuck on the same issue after upgrade from PVE 7.4 to PVE 8.2. Stuck on kernel 6.8.8 boot. After several attempts to boot with different kernel options I have found that the kernel option pci=nomsi allows to boot. Also full disable of ASPM allows to boot. I have stopped on pcie_aspm=off

GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"

 

[iprigger]

I have old HW:
8 x Intel(R) Xeon(R) CPU E5630 @ 2.53GHz (1 Socket) - 16GB
Intel S5500BC

Stuck on the same issue after upgrade from PVE 7.4 to PVE 8.2. Stuck on kernel 6.8.8 boot. After several attempts to boot with different kernel options I have found that the kernel option pci=nomsi allows to boot. Also full disable of ASPM allows to boot. I have stopped on pcie_aspm=off

GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"

Hi,

Thanks... i will definitively try that one next time I am going to reboot the systems at that customer.

Tobias

 

[dbottaro]

That shouldn't be necessary, in my opinion. I think with the way the Broadcom/VMware debacle has gone, Proxmox is going to see a LOT more traffic. They need to absolutely NAIL getting a new machine up and running. This experience was terrible, and I ended up going back to vSphere.

I had a working hypervisor in 10 minutes.

This issue is directly related to the Linux kernel on specific systems. I had a working Ubuntu 24 installation running beautifully on a Dell T140 until a the kernel updated to 6.5, then I had this same exact behavior, I pinned the kernel version in GRUB to solve the issue. I will now use this x2ACPI solution to enable the server to run the latest version of Proxmox.