Recent content by Tail870

It just hit me that mpt3sas not the main reason why suspend is broken since that issue occured on both kernels but something in Proxmox in general...

I just tested installing Proxmox on Debian 12 w/o removing kernel (so I can test it with Proxmox packages). Both Debian 6.1 and Proxmox 6.8 kernels now resets host instead of waking from suspend... Which means that kernel itself shouldn't be the culprit.

Info about PCI-device: :~# lspci -vvv -s 01:00.0 01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Subsystem: IBM SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-...

Hello! I'm using Proxmox VE 8.3-1 with LSI 9200-i8 card (this exact model on AliExpress). When I'm trying to wake up host from suspend mode (systemctl suspend) it just resets. Tried kernels 6.8 (default one) and 6.11. At this moment only thing helps is blacklisting mpt3sas module. But sleep mode...

So, if I use 32 GB of RAM for a single VM I should use 64 hugepages? Or it's preferable to set [total RAM GB] minus 1-2 GB for Proxmox itself? UPD: Silly me. It means, like, 2-4-8-16-etc, right?

Thanks a lot! Your post helped me a lot. But I have a question: currently I'm using this grub-string: GRUB_CMDLINE_LINUX_DEFAULT="mitigations=off default_hugepagesz=1G hugepagesz=1G hugepages=0" In hugepages=<num> how should I calculate a num parameter? Or zeroing it is fine?