Search results

  1. L

    The Reasons for poor performance of Windows when the CPU type is host

    Have you tried setting the CPU type to EPYC-Genoa? According to the best to use for you would be either EPYC-Genoa or x86-64-v4 (enables AVX512)
  2. L

    The Reasons for poor performance of Windows when the CPU type is host

    Please add it to the guides like https://pve.proxmox.com/wiki/Windows_2022_guest_best_practices
  3. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    Okay so we have more instances of Intel CPU bug related crashes now: My instance of Intel 13900 CPU crashes here in this thread (motherboard: ASRockRack W680D4U-1L) Another one @dakralex showed me here with Intel 13900K: https://forum.proxmox.com/threads/153793/ by @Crash1601 Another one I've...
  4. L

    Random freezes, maybe ZFS related

    Hello fellow Intel 13900 user. I already had a similar problem on one server on November 27th 2024 (https://forum.proxmox.com/threads/kernel-panic-after-upgrade-to-8-3-kernel-stack-is-corrupted-in-kmem_cache_alloc-0x37b-0x380.158134/#post-727767), now I got another problem on a different server...
  5. L

    [SOLVED] pvestatd.service: Main process exited, code=killed, status=11/SEGV

    Ja, bei mir lag es in der Tat ebenfalls an der Hardware. Mit neuer CPU+Mainboard+RAM+SSDs läuft der Server fehlerfrei! Siehe https://forum.proxmox.com/threads/kernel-panic-after-upgrade-to-8-3-kernel-stack-is-corrupted-in-kmem_cache_alloc-0x37b-0x380.158134/#post-727767
  6. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    The old server hardware was faulty! At first, Hetzner tried to keep the old hardware and just do some settings in the BIOS (which looked promising too): But directly after a fresh PVE 8.3 install, I got the same old error again: Therefore I chose the option to change all hardware, including...
  7. L

    [SOLVED] pvestatd.service: Main process exited, code=killed, status=11/SEGV

    Hey da geht es dir sehr ähnlich wie mir und einem Hetzner EX-101 mit Intel 13900 CPU. Habe lange memtest86, Disk Checks und CPU Checks gemacht, alle fehlerfrei und ohne Anzeichen von Problemen...
  8. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    Wow this looks super similar to my PVE 7 test at https://forum.proxmox.com/threads/kernel-panic-after-upgrade-to-8-3-kernel-stack-is-corrupted-in-kmem_cache_alloc-0x37b-0x380.158134/post-727108 I got some general protection fault and lots and lots of segfault instances, too. So that's it -...
  9. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    I don't have 8.1 to try, but installed PVE 7.4-1 from https://enterprise.proxmox.com/iso/proxmox-ve_7.4-1.iso Installation is a pain, had to use the quirks from https://forum.proxmox.com/threads/generic-solution-when-install-gets-framebuffer-mode-fails.111577/#post-541768, and for some reason...
  10. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    PVE 8.2 has the same problem, directly after installation. So I guess my "system" (CPU? memory? I have no idea anymore, because my stress tools havn't found any problems) is somehow instable. At first Hetzner provided me with the wrong USB stick, a PVE 8.3 again, so I've installed that one and...
  11. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    before testing PVE 8.1/8.2 again, I did some further CPU tests overnight: # 1 hour test CPU root@rescue ~ # stress --cpu 32 --timeout 3600 stress: info: [33029] dispatching hogs: 32 cpu, 0 io, 0 vm, 0 hdd stress: info: [33029] successful run completed in 3600s # 15 hours test CPU root@rescue...
  12. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    This is the result of Hetzner's Full Hardware Check: Dear Client, The hardware check was completed without any errors. Please see the results below: -----------------%<----------------- Hardware Check report for IP xx.xx.xx.xx CPU check: OK CPU 1: OK Temperature: OK Clock speed: OK...
  13. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    Thanks a lot for your replies! Before doing further testing, I had already asked Hetzner for a BIOS/UEFI upgrade, and apparently they did something, see Release Date from 2024 (I rent the server since 3/2023, and it was never down for any maintanance from Hetzner, so they must've done it): #...
  14. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    Here another screenshot from another crash: Here another one: Another one: Another one: I have some more but I think they all look pretty similar. Is the server hardware somehow faulty? Or is it a Proxmox problem, like PVE 8.3 being not compatible with this system? In case of a...
  15. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    That's not the problem. I've just installed PVE https://enterprise.proxmox.com/iso/proxmox-ve_8.3-1.iso on the same server freshly: After installation I directly encountered the same problem again: Then after a hardware reset, the system booted surprisingly without a problem. I've entered...
  16. L

    Kernel Panic after Upgrade to 8.3 (Kernel stack is corrupted in: kmem_cache_alloc+0x37b/0x380)

    Today I tried to upgrade a server (Hetzner EX101, with Intel i9-13900) with PVE 8.2 to 8.3 via the Web GUI. The server is not part of a cluster. I can provide you the PVE license number if needed. Hardware configuration: 2x 2 TB NVME in ZFS RAID1 (root), 2x 8 TB NVME in ZFS RAID1 (for PBS...
  17. L

    Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6

    Einer meiner PVE hosts war nicht mehr via Web GUI erreichbar, ist komplett gecrasht (im Syslog stundenlang keine Einträge mehr) also habe ich den Hetzner "Automatischer Hardware-Reset" genutzt, um einen Reset auszulösen und das System neu zu starten. Ich habe folgendes in /var/log/kern.log...
  18. L

    How to stop syncjob flooting syslog

    thanks for the quick reply. I've opened https://bugzilla.proxmox.com/show_bug.cgi?id=4646
  19. L

    How to stop syncjob flooting syslog

    To be precise: The sync job on host A (which pulls data from remote host B) does cause lots of proxmox-backup-proxy logging on host B, not on host A. I have the same problem, because several servers sync data from a host about every 5-10 minutes, so on the host that data is being pulled from I...
  20. L

    Generic Solution when install gets FrameBuffer Mode Fails

    Thanks a lot for your solution, and the details! I just want to add some detailed instructions, and provide another example of bus IDs, so maybe my example helps out someone: I am using the brand new Hetzner EX 101 which includes a Intel® Core™ i9-13900, and tried to install Proxmox...