Search results

  1. G

    Severe Download Speed Limitation on Newly Provisioned VMs and CTs (Proxmox 8.4.1)

    Related ? https://help.ovhcloud.com/csm/en-de...?id=kb_article_view&sysparm_article=KB0066095
  2. G

    Windows 11 VM BIOS change anyone?

    I forget the mandatory disk layout conversion from GPT to MBR. I can't help you on this topic on my free time, but you will find examples on the web. It's same as Windows 10, switch from UEFI to Legacy/CSM. Don't forget to backup VM before attemps.
  3. G

    Windows 11 VM BIOS change anyone?

    yes in hardware option, but Windows require boot loader adjustments, not really a Proxmox VE side. edit2: GPT to MBR disk layout conversion required too. edit: Windows 11 officially require UEFI but works in SeaBIOS (+ clean install / inplace upgrade from win10 require bypass)
  4. G

    DISK IO Rate comparison wrt to VMWare VMs for NvME SSD

    I don't think OP use qcow2 as "Format" is greyed out to raw , which confirm it's already block based. @kunwarakanksha : is ZFS or Lvmthin ? is BIOS server power/energy set to Maximum performance ?
  5. G

    Local Space Used

    Size reported is the whole partition size where folder is stored. By default with ext4/Lvm install, this is the whole Linux OS system size + the stored iso.
  6. G

    AMD : BSOD unsupported processor since Windows build 26100.4202+ ( update kb5060842 + its preview kb5058499 )

    reproducible on "Ryzen5 PRO 4650GE" (~Zen2) / PVE 8.2.2 / PVE-QEMU 9.0 / Kernel 6.8.4-2 by the way I use mitigations=off on both systems. Cumulative Windows Update June 2025 is kb5060842 for both Windows 11 24H2 and Windows Serveur 2025. cpu type "host" can't be used.
  7. G

    AMD : BSOD unsupported processor since Windows build 26100.4202+ ( update kb5060842 + its preview kb5058499 )

    reproducible with today cumulative June 2025 update. Windows 11 24H2 + Windows Server 2025. BSOD unsupported processor if cpu type is "host" ( AMD EPYC 7302 release date mid-2019 + PVE 8.4 Kernel 6.8.12-9 )
  8. G

    Abysmally slow restore from backup

    is local restore can be improved by your patch ? I mean PBS installed alongside PVE where network is over localhost ?
  9. G

    Abysmally slow restore from backup

    That's a big patch ! your binary size is 187 MB where original is 6.8 MB put me off to try.
  10. G

    VM corruption during PBS backups – still an open issue in 2025?

    Main issue is when PBS is too slow, like doing backup directly over WAN. Or like multi backups to one HDD. If you use incremental SQL backup system, set the VssOption option to the numerical value of 5 in Windows registry to not break the SQL chain backup...
  11. G

    Ghost Disk

    nothing seems wrong. sdb in your VM is a virtual disk allocated in your nvme disk in directory storage called Plex. what did you expect ?
  12. G

    nvme IOPS 4k performance - same disk with diffrent Host = diffrent results.

    AFAIK, vDisk is currently limited to one qemu thread, which is limited to one cpu thread. https://forum.proxmox.com/threads/feature-request-proxmox-9-0-iothread-vq-mapping.166919/
  13. G

    nvme IOPS 4k performance - same disk with diffrent Host = diffrent results.

    265K is last intel CPU (late 2024) where Single Core raw compute is about 2,5 times the Epyc 7702 Single Core raw compute (late 2019). Epyc is slower with only 1 VM , but do the same test with 32 concurrent VM
  14. G

    AMD : BSOD unsupported processor since Windows build 26100.4202+ ( update kb5060842 + its preview kb5058499 )

    Not reproducible on Win10 22H2 neither Win11 23H2 (each with their Preview Update Late May 2025 ) Only with Preview Windows Update Late May 2025 for 26100 build ( used by Windows 11 24H2 and Windows Server 2025 )
  15. G

    AMD : BSOD unsupported processor since Windows build 26100.4202+ ( update kb5060842 + its preview kb5058499 )

    Reproductible on Server 2025 too, as same build 26100 as Win11 24H2 (AMD Epyc 7302)