Proxmox is so unstable right now that I have shut down my home server (with everything on it) and just have to wait until a stable kernel and version is released. I have used Proxmox for about 8 years and this is the most unstable it has been for me. I don't have the time right now to reinstall...
I had to shut my proxmox server down due to instability with random crashes after the recent updates to the kernel and the base software. My server runs everything from files to web pages, to the vyos router. I tried using the 6.5 kernel and it worked for a few days and then crashed again. The...
I installed 6.8.5.3 yesterday and my server froze after a few hours. Had to hard reset it and it would freeze again after a few hours.
Kernel 6.8 is too unstable for me. I have now reverted to kernel 6.5.13-5.
The easiest option right now is to reboot the Proxmox server and select the previous kernel at boot - you need access to the vga out of the server or use IPMI. You can set the default boot in systemd-boot as above - using 'd' during boot - if you really need to have a default. If you have grub...
This is a really good solution. The only issue is that one needs to have access to the video out or IPMI of the server to set the default boot.
Would be better to have a method to make a default boot setting via SSH etc. in a running Proxmox environment.
I also have the same issue after upgrading to kernel 5.13.19-4
My linux VM's boot fine, but a windows 10 and a windows 11 vm do not boot. Strangely a windows server 2019 vm does boot fine.
I had to revert back to kernel 5.13.19-3 to get everything working again.
It would be really nice if...
@Ramalama Great work!
I'll give your new kernel a try when I get a chance on my AMD Ryzen Zen 3 setup.
Which version of QEMU are you running it with? (pve-qemu-kvm)
Did you include support in the kernel for ZFS 2.0.3 as well?
To the Proxmox DEVS - it would be really good if you could include...
Yes, but this is not solved. pve-manager 6.3-4 has issues that need to be fixed. Your solution is only a work around and Proxmox should look at fixing 6.3-4.
I also have similar issues. There are some serious stability issues with the recent updates. You have to either reinstall from the ISO or roll back every package to get a stable system. The potential problem packages are the updated kernel and QEMU I believe. Also look at your system services...
Unfortunately I reinstalled pve from the iso and didn't keep any logs.
This thread details the RDRAND issue and the boot parameters needed to disable it: https://forum.proxmox.com/threads/a-lot-of-errors-systemd-kernel-on-newer-hardware.84758/
I'm sure the VM issues were related to QEMU 5.2 as...
I'm running PVE on a 5950x and the vanilla install with the the most recent iso from proxmox worked well (proxmox-ve_6.3-1.iso).
There is also a dependency on your motherboards bios AGESA version - mine is (ComboV2 to 1.1.0.0).
However after installing I ran a PVE update and it pulled in kernel...
Thanks Ramalama and Thomas for responding.
Normally I would spend a lot more time on this getting it sorted out but since I have the kids at home on lockdown and the internet is needed for school, I had to wipe the update and reinstall PVE from the iso. So right now I am going to wait a long...
Hi,
I have very similar hardware:
MB: Asrock Rack X570D4U-2L2T
CPU: Ryzen 5950x
I updated PVE this morning with the new kernel (5.4.98) and it has taken my system from being stable to completely unstable. The previous kernel was (5.4.78).
I suspect this is mainly caused by the unstable Intel...
I also tried a reverse proxy via a sub-directory with apache and couldn't get it to work. Similar to LnxBil, I managed to get it working without any modifications with a new virtual host instead.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.