Search results

  1. I

    CPU performance on proxmox VM

    So, the way to go is 30 vCores with cpulimit=30.
  2. I

    [SOLVED] Option --transfer-last kann nicht rückgängig/verändert werden

    @shanreich Ja so habe ich mir das eh gedacht. Spiesst sich hier halt mit der Funktion Werde halt die Namespaces hin- und her syncen, dann passt das. Einen Feature-Request mit der Funktion Re-Sync gibt es ja schon. Danke!
  3. I

    [SOLVED] Option --transfer-last kann nicht rückgängig/verändert werden

    Hallo an alle, musste einen defekten Offsite/secondary-PBS neu installieren, so weit alles gut. Um relativ schnell wieder alle Namespaces gesynct zu bekommen, habe ich die Funktion im Sync-Job benutzt. Soweit alles gut, nun sind alle Namespaces mit den letzten 3 Tagen gesynct. Nun wollte ich...
  4. I

    ZFS Raid 10 mit 6 Samsung PM893 1,92TB Sata Schreckliche Schreibraten

    Nur so zur Info, wurde die aktuellste Firmware auf den Samsung´s gespielt? Da gibts nämlich so einige Korrekturen...
  5. I

    VMs got down While running a backup

    I had this issue when the Backup-Storage was too slow/stalls/timed-out. You should look into this.
  6. I

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    There´s some Problems with the 6.2 Kernel. Not only Windows-VM´s are affected, we also experienced some weird random behaviours spreaded across different locations. KSM, Qemu, Network-related things etc... Hopefully the 6.2 gets mature as soon as possible.
  7. I

    ceph-crash problem

    Done all but does not solve the remaining issue. So, manual deleting was the only way to get rid off the annoying messages in syslog..
  8. I

    ceph-crash problem

    yes, on all nodes.
  9. I

    ceph-crash problem

    So i deleted these annoying things and it´s silent now. ;)
  10. I

    Proxmox + ZFS + HP P440ar on HBA mode

    @auranext did you ever solve this issue?
  11. I

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    Just for my case: It was a Windows-Problem -> Disk-Error (in the related VM). Also restoring the VM from Backup does not solve the issue. So i had to boot the VM via Windows-Install Disk and force a checkdisk (found some errors). After that the VM boots up without any issues.... Crazy world...
  12. I

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    Thanks, but what is the Solution?
  13. I

    Windows VMs stuck on boot after Proxmox Upgrade to 7.0

    Wow, same here. :eek:
  14. I

    Proxmox VE 8 Update danach Fehler

    So sollte es aussehen: UUID=354b626f-30f1-4cc6-a3a6-c7192a7eb1ad /mnt/pve/omv-music ext4 defaults 0 0
  15. I

    Proxmox VE 8 Update danach Fehler

    Hatte ich auch, liegt aber am letzten "1". ändere den Eintrag auf "0", zB.: /dev/sdb /mnt/pve/omv-music ext4 defaults 0 0 Grund: PVE will einen fsck machen, bevor der Mountpoint gemountet wurde. Somit beisst sich die Katze irgendwann in den eigenen Schweif ;)
  16. I

    ceph-crash problem

    Same here.
  17. I

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    I hope so... ;)
  18. I

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    Searched an Host with the same CPU and here it is: root@pbs-dc1:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 28 On-line CPU(s) list...
  19. I

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    This size applies only to our Database Servers... Hmm, mitigations=off is set up everywhere here.
  20. I

    [SOLVED] Proxmox 8.0 / Kernel 6.2.x 100%CPU issue with Windows Server 2019 VMs

    "Just 64GB RAM" because its just an example-VM that doesn´t need more. Single-Socket because the Hardware is on an AMD Milan, this is a Single-Socket-Blade with 48 Cores. CPU-Limit -> simply to limit the VM ;)
Top Bottom
Back