Search results

not Cstates at all. only Cstate 6, for your specific bios you need to read the manual or google, how the options is actually called. disabling Cstates completely only, if nothing helps or your board does not have an option to perform typical power at idle (to disable Cstate 6, which is new and...

Dell R7525 is AMD Epyc, here we go again and again: https://forum.proxmox.com/threads/proxmox-keeps-crashing.117837/post-511345 https://forum.proxmox.com/threads/opt-in-linux-5-19-kernel-for-proxmox-ve-7-x-available.115090/post-507337

Sorry digging this thread out, have a similiar situation. Is the postfix mynetworks (main.cf) + smtpd_recipient_restrictions=permit_mynetworks (master.cf) not sufficient to open port 26 from outside? Thanks in advance.

@drx1, macos is not supported by any virtualization that is not running on apple hardware and has corresponding licenses. your issue is not proxmox side, not the passthorough. it is really hardware issue (apple vs nvidia, there are no webdrivers from nvidia anymore, and no official drivers for...

ah, here you go, K2200 inital support Yosemite, last support High Sierra https://dortania.github.io/GPU-Buyers-Guide/modern-gpus/nvidia-gpu.html#maxwell-series-gtx-9xx-745-750-ti

You can't use a Nvidia GPUs with MacOS since years. Want a hackintosh, baremetal or virtualized with gpu passthrough, you should ask in corresponding places. AMD RX580, RX5700XT and RX6900XT is the way to go for now (RX7900 not supported yet and probably will never be). But Apple could drop...

Hi kstoilov, sadly, no.

already plan to do that at weekend, very excited!

just fyi: this will disable turbo boost and power management for your cpu at all, so you run all your cores permanently at base frequency... and yes, it is indeed a workaround, better than crashes all the time. if there is no other way to disable cstate 6 on your mobo, it is acutally the only...

Ok, if you did the above, please open a new thread for you issue. I see from your last log, that BTRFS cache helper is crashing. that might be indeed a different issue, but soft lockups with amd cpus are usually cstate 6 (in 99%). While there is also a possibility, if you are running non-ecc...

AMD CPU and "cpu soft lockup" is what i told above. no need to go through all the debugging every time someone didn't used search.

I don't know how many times to post that... If your CPU is AMD ZEN2 or ZEN3... (Ryzen 3xxx and 5xxx, and probably older and newer as 2xxx and 7xxx and all their counterparts of Threadripper and Epyc Series), try first following... (just use search "ryzen crash", you find all of that). Enjoy...

hm, that sounds strange. i have dozens of ryzen 5950x and a few epyc 72xx/73xx nodes. the only other possible stability issue i experienced so far, is OOM with ryzen (not with epyc)... since ryzen is limited to 128gb ram, it happens fast to max that out, considering 16c/32t and all the caches...

Again, if CPU is AMD Ryzen/Threadripper/Epyc gen 2 or 3, please try that first: https://forum.proxmox.com/threads/o...ox-ve-7-x-available.115090/page-3#post-507337 Kernel downgrade doesn't help. If CPU is some Intel, use search for crashes with intel. Maybe this should be sticked (with better...

https://forum.proxmox.com/threads/opt-in-linux-5-19-kernel-for-proxmox-ve-7-x-available.115090/page-3#post-507337

Hello, after upgrade to ceph quincy 17.2.5, the log spamming not going down by ceph tell mon.* injectargs '--mon_cluster_log_file_level info' + restart mons. after reading ceph docs, quincy is now only supporting boolean true/false for the above config, i don't want to disable logging at all...

for your initial configuration you eiher keep your first physical nic unchanged (so in management vlan tagged on switch) or you have console access to your host (i.e. remote management ilo/idrac/ipmi, physical display and keyboard...) or be careful at applying network changes, so you don't...

@Jez2022 yep, again, you can do what you request. a bit complicated, but absolutely worth it. one single physical nic to your vlan capable (and preconfigured) switch _trunk_ port (untagged). on proxmox host side you tick the "vlan aware" option on your VMBR0 (Linux Bridge), then for management...

uh, i am curious, you have kvm64 cpu on that VM, or host, or any other option?

if you have a vlan capable switch, you could use the second nic as trunk to switch (untagged) via vlan aware linux/ovfs bridge. on the switch tag the ports for wan and lan. in pfsense create according vlans and assign your wan and lan interfaces to them.