Recent content by _gabriel

  1. G

    Server-Disk I/O delay 100% during cloning and backup

    if these are Samsung QVO, they are not suitable at all. QLC drives write very slow after cache (which is different from DRAM cache). There is plenty topics on the forum about it, mainly with ZFS because it reveals faster the slowness.
  2. G

    Server-Disk I/O delay 100% during cloning and backup

    it's expected as they can't substain writes.
  3. G

    Problems with some VMs imported from ESXi

    Windows may require to boot once into Safemode to "re-enable" standard sata controller driver.
  4. G

    W2025 virtio NIC -> connection drop outs

    you need to find what to fix, as it's not virtio nic problem.
  5. G

    Wireguard Client in LXC: SSL 525 Error (Cloudflare) - Config Works on Other Systems

    Sorry, I've no experience with Cloudflare, but I don't see where Proxmox Ve can be the problem.
  6. G

    Persistent VM instability with Ryzen 9 9950X3D and Proxmox 8/9

    what about CPU usage inside VM ? is there a process high CPU usage ?
  7. G

    W2025 virtio NIC -> connection drop outs

    have you tried without Multiqueue to dig out ?
  8. G

    W2025 virtio NIC -> connection drop outs

    so title shoud be "windows virtio version 285 connection drop outs" try without setting Multiqueue
  9. G

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

    I don't believe people using WSL to run such task. there is rsync Windows binary.
  10. G

    PVE9 New server bad performance NVME Gen5

    try with Lvmthin as ZFS has overhead, can't be compared to baremetal even more in benchmark. Numbers should be closer if you run multi VM at same time, that's the point of virtualization. For single VM ...
  11. G

    W2025 virtio NIC -> connection drop outs

    Test with Windows Server 2022
  12. G

    [SOLVED] Unable to install proxmox on a server where it previously worked.

    have you checked if ip answers even if console looks wrong ?
  13. G

    VM en erreur : io-error

    merci pour le retour. ce n'est pas une question de bios. 1 To sera toujours égal à 931 Gio. Les constructeurs ont toujours compté l'espace de stockage en base décimale, 1000 octets = 1 Ko Alors que les données sont décomptées en base binaire où 1024 octets = 1 Ko ( de plus en plus noté...