Recent content by hardwareadictos

I can confirm similar behavior on a 4-node cluster running Proxmox VE 9.2.2. Cluster hardware: 2x Intel Xeon E3-1220L v2 1x AMD EPYC 7551P 1x AMD EPYC 3251 Only the EPYC 3251 node is affected. Symptoms: Progressive performance degradation after ~2 days uptime on kernel 7.0.2-6-pve CPU...

Well, rear weeks without any news i just mailed proxmox about the issue and i got this response: Near a month later nothing has changed so i opened this issue on proxmox bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=6836 Please, feel free to discuss on the opened issue and provide...

Already reported there: https://forum.proxmox.com/threads/problems-with-gpu-passthrough-since-8-2.145917/page-5 For the moment, administrative silence...

Did someone test if this issue is mitigated on PVE9 and 6.14 kernel? Edit: Spent all the morning trying to make v6.8 and v6.14 work with my T1000 passthrough without success, tried relaxed settings, various grub cmdline configs and tried to involve chatgpt. Updated my M11SDV-8C+-LN4F bios to...

I was really happy because nvidia announced that GRID v16.9 is compatible with 6.8 kernel so i updated to be able to use my P4s and now i see than AMD and Supermicro broke the PCI passthrough of my T1000 on my M11SDV-8C+-LN4F on that kernel.... Instead of flashing old BIOS or dealing with mobo...

Hey! Try this: https://forum.proxmox.com/threads/gpu-passthrough-issues-after-upgrade-to-7-2.109051/post-469855

Hey, good morning all :) One week ago i moved one wireguard LXC container and one Pihole container from a 2xDell R210II clúster to an AMD Epyc 3251 single node (My production server), and now those containers are suffering from high CPU load average without any aparent reason: On the cluster...

Just to add some more information: Added two votes on the primary host by rising expected votes and config version on corosync.conf which is applied successfully and persistent across reboots, for some reason this configuration is not replicated on the secondary host. For the node number 2...

Edit: Just checked it yesterday and no hosts file anomalies and primary nameserver is outside cluster hosts (it's on another separate proxmox host)

Thank you @UdoB :) On my case i didn't move any nameserver or modified the hosts file, i just made a OS update from web GUI. Will check later those and report back anyways. Thank you!

Rear two days of testing, no more temp spikes. Thanks a lot for guiding me :)

THANK YOU Just managed to get my GTx 970 working with step 4 and the hookscript for rebinding, for some reason putting it on cron didn't work. @nick.kopas hookscript attatched to my vm worked fine :)

Good morning Just updated yesterday throw GUi my Proxmox packets on my two node cluster. For some reason my nodes cannot live together on the cluster anymore: Time is synced on both servers. Corosync config wasn't modified: Tried restarting proxmox core services with no luck: service...

Thanks a lot. Testing in progress :)

And thats what happens when i run the rescan script manually and i boot the vm: This ends on a Proxmox host freeze. For me the only way of making my GTX 970 working is to rollback to 5.13 kernel. @WesC did you find any improvements on the mainline kernel?