Recent content by Joris L.

in the meantime, consider disabling nested virtualisation, i remembered this helped for a past instance of Proxmox instability. basically, run this command from shell for the matching CPU module check with: lsmod | grep kvm to determine if it is an AMD or Intel CPU module loaded check...

seems unrelated but I have similar issue with Proxmox 8.x running on a single-node, never had that with Proxmox 7.x as far as i remember with 8.x it seems undiagnosable and unfixable

it is likely the freeze happens between 17-19 days of uptime, correct ?

was this by coincidence on a VM running Debian?

I've ran Proxmox without issue for months on end, until version 8. nothing but problems with freezes. The maximum lifetime i get now is 19 days, typically a 'freeze' happens between 17-19 days of uptime. Symptoms: - the system reponds to ping - login works but does not complete - the system...

Since this is not a first I share here a brief summary of an awful event which lead to considerable downtime. Running a Proxmox cluster with OPNSense as firewall, this firewall is the first point of entry for all traffic. Yesterday I switch off routers (1 ISP and 1 wifi router) as I did before...

Thanks for sharing. This does give some food for thought. Notable is non of the kernel boot options prevent the display output capture and this is apparently a known issue. Thinking of it, it seems logical to not set virtio-GPU for display under hardware, I now vaguely remember that's how it...

asking for your advice and experience (AMD Radeon VII GPU) when booting a VM with the GPU mapped as virtio-GPU this causes the VM boot screen to be displayed on the console of the server, this is not desirable. after the VM captures the GPU this prevents from switching to a different TTY using...

@zenowl77 you should really just benchmark it from a live system or similar, may take some work to make it work but it will save you headaches and useless efforts, test it as a dedicated device, no Proxmox/vGPU/... involved

Looking at the X299 product page I notice the last BIOS is from 2021, I'd not look much further. One thing you could do is boot the machine with a live system or similar and benchmark hashcat that way on the GPU. I'd not be surprised if the performance you get from this is as high as it is...

looking at this @guruevi could be right the memory lay-out may be causing performance issues (96GB of ram) (32+32+16+16 ?) best is to consult the motherboard manual to find how the ram is assigned and also to check if all ram is compatible also, not all ram slots are equal for any kind of pair...

I'd agree for a 3D benchmark or something else media-heavy, for hashcat I've not seen much variance in compute benchmarks regardless of the slot. Also, unless the system is under stress test or this is indeed loaded to the max any performance issues due to bus constraints are unlikely. In...

if you use the card without vGPU you're likely to see performance similar or at times higher than bare metal, my experience with the Radeon card

MTU is a known source of issues with auto-negotiate, check if there are errors on the interfaces or if duplex is switching for the interfaces. I agree it could be elsewhere, typically poking around low-level and moving up the stack is 'the way' to diagnose network/vendor issues. Mikrotik is also...

UPDATE based on researching logs and error messages journalctl -b all -p warning -f I've come to the "educated assumption" the issue is likely either entirely unknown at this time or it is caused by the Debian VM /dev/sda I/O errors replicating onto the Proxmox VE ZFS leading to system...