Just chiming in here to say this: That's normal. You are using GRUB as your bootloader then (that should be the default unless you are booting a UEFI system with a ZFS root partition). systemd, among other things, acts as the init system in Proxmox, i.e., the process that is the ancestor of all other processes. So it will always show up as PID 1 and, thus, on top ofefibootmgr -v this should say grub mine does. But I still get systemd under pstree.
pstree. Under the systemd umbrella of software projects there is also systemd-boot (formerly, gummiboot) which we use as a bootloader if you are using ZFS on your root partition. Please note though that systemd ≠ systemd-boot and that having systemd showing up as PID 1 does not imply that systemd-boot is being used.
 
	 
	 
 
		

 I even tried switching to the kernel you are using same issue. I think its a Cstate issue as I mentioned before. Cores go idle and then they start going to sleep and then things freeze up. I will disable the c-states in BIOS see if it stays up. This only happens after the system has been sitting idle multiple hours. But could be issue for both versions of kernel.
 I even tried switching to the kernel you are using same issue. I think its a Cstate issue as I mentioned before. Cores go idle and then they start going to sleep and then things freeze up. I will disable the c-states in BIOS see if it stays up. This only happens after the system has been sitting idle multiple hours. But could be issue for both versions of kernel.