Recent content by ermanishchawla

  1. E

    IPERF3 not exceeding the bandwidth beyond 10G even if proxmox hosts are connected on 25G

    The issue is resolved, it is because of the wrong interface selection
  2. E

    IPERF3 not exceeding the bandwidth beyond 10G even if proxmox hosts are connected on 25G

    iperf 3.18 (cJSON 1.7.15) Linux inc2pve1 6.17.9-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.9-1 (2026-01-12T16:25Z) x86_64 Optional features available: CPU affinity setting, IPv6 flow label, SCTP, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing, authentication, bind to device...
  3. E

    IPERF3 not exceeding the bandwidth beyond 10G even if proxmox hosts are connected on 25G

    Sender Side iperf3 -c 10.XX.YY.8 -u -b 10G -i 1 -t 10000 -P2 Connecting to host 10.25.240.8, port 5201 [ 5] local 10.25.240.7 port 49254 connected to 10.25.240.8 port 5201 [ 7] local 10.25.240.7 port 48981 connected to 10.25.240.8 port 5201 [ ID] Interval Transfer Bitrate...
  4. E

    Proxmox VE 8.2 released!

    Yes you are right, missed in between lots of other stuff to read. Anyhow better would be that it shall automatically update the /etc/network/interface files over a reboot to reflect the changes (if possible)
  5. E

    Proxmox VE 8.2 released!

    There is an issue with the upgrade. Post upgrade network interfaces names have change pre upgrade ens4f0 Post upgrade ens4f0np0 This has caused all user created bonds to go down Needs to modify the network config file to bring up the nodes
  6. E

    Ha not working proxmox 8.0.3

    After restarting pve-ha-lrm ha service is working
  7. E

    Ha not working proxmox 8.0.3

    Vm configured in ha is not starting but when I remove the configuration from ha and then run it manually, vm is running
  8. E

    Network down after upgrade to proxmox 8 beta

    Issue is resolved deleting ntpsec file from if-up.d folder solved it
  9. E

    Network down after upgrade to proxmox 8 beta

    Dear All, We have upgraded our servers to proxmox 8 beta version and after installation everything was working fine and once we have rebooted the hardware It was showing cleaning orphan node and was stuck there for quite long Initially we thought filesystem is corrupted and it will clean and...
  10. E

    Invalid/wrong statistics during migration

    If that is the case, the word "of" in the sentence is misleading 147Gb of 97Gb Stating clearly is better I believe Memory state is lagging, transfered:147GB, Actual Required: 96GB
  11. E

    Invalid/wrong statistics during migration

    I know the reason, why it is happening, I am only asking why it is showing wrong transferred 147.2 GiB of 96.1 GiB VM-state, 274.3 MiB/s 147 out 96 is not possible
  12. E

    Invalid/wrong statistics during migration

    2022-09-05 08:07:51 migration active, transferred 146.3 GiB of 96.1 GiB VM-state, 412.7 MiB/s 2022-09-05 08:07:52 migration active, transferred 146.7 GiB of 96.1 GiB VM-state, 335.0 MiB/s 2022-09-05 08:07:53 migration active, transferred 147.0 GiB of 96.1 GiB VM-state, 315.0 MiB/s 2022-09-05...
  13. E

    Invalid/wrong statistics during migration

    While migrating a VM from one node to another, the statistics are shown, which are wrong, please check attachment
  14. E

    (Unofficial) Proxmox VE VDI Client - Initial Release!

    Hi, I want to know if a user is allowed to access 3 VM's in cluster, I want to restrict access to specific VM if he access from specific machine but allow him to access all VM's if accessed from another system In short IP based/configuration based filtering based on system local config Feature...
  15. E

    Proxmox VE 7.2 released!

    Thanks checked the git, bump version is pending Tried erasure code pool, performance is better than RF=3 in benchmark, testing more on load and per VM