longer's latest activity

  • L
    So at the moment, the daemon successfully restarted, and running for more than hour. Looking at journalctl may provide related information, so the last crash from shared crash info was at 2026-07-27 23:21, therefore take look what happend before...
  • L
    Not really sure, but did you verify different port portv2 and v3 to see if any differences? Just my 2 cent, Do you have IPMI/iDRAC? maybe you can attempt from IPMI console and check this issue after booting.
  • L
    longer replied to the thread VirtIO Block or IDE.
    The recommendation is to use virtio dirvers for best performance: https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices In the wiki its also mentioned: "the latest VirtIO iso do not include drivers for Windows 2003. You need to download...
  • L
    Is it always mon.pve2 ? You could attempt to destroy and create this mon in case other mon are fine. Could you also share: ~# ceph status
  • L
    longer replied to the thread Server 2025 High CPU.
    Is the high CPU usage showing up inside the Windows Guest (Task Manager), or on the Proxmox Host GUI? If inside the Windows VM What specific process is consuming the CPU? I would suggest to test to: - Increase the assigned core to e.g 8 cores...
    • testing.png
  • L
    longer replied to the thread Server 2025 High CPU.
    hmmm there currently known issue explained in: https://forum.proxmox.com/threads/windows-server-2025-cpu-suddenly-at-100.184763/post-861490 Where its recommended to use CPU type other than host CPU. So you can roll out this and keep CPU type as...