Search results

  1. spirit

    [SOLVED] VXLAN ARP timeouts

    I 'm not sure that hook can work with live migration, as the arp entry need to be set after source vm stop (the arp entry need to be flushed from source horst) and before the resume of the target vm. This is a thing that we should implemented officially. (like we already do for mac address with...
  2. spirit

    I/O stall while backup to PBS is running and fdatasync failure after backup fails

    try to enable fleecing option in backup scheduling advanced option. when backup is running, the new writes are going first to the pbs storage and that can give you slowdown if the pbs is slow or have more lantency or have limited bandwidth. The fleecing option is creating a temporary disk on a...
  3. spirit

    Ceph - VM with high IO wait

    If can really confirm that memory allocator impact librbd latency. you can with a simple fio 4k randread or write. my last qemu patch from 2023 : https://lists.proxmox.com/pipermail/pve-devel/2023-May/056815.html default malloc: 60k iops 4k randread tcmalloc : 90k iops 4k randread (can be...
  4. spirit

    live migration: ram_save_setup failed: Input/output error

    for hardening, you can do something like DisableForwarding yes Match User root Address <<10.0.10.0/24,10.0.20.0/24>> DisableForwarding no AllowTcpForwarding yes X11Forwarding no AllowAgentForwarding no PermitTunnel no (replace network address by your proxmox management subnet)
  5. spirit

    Corosync link flapping with 3 nodes

    So, here, at 22:04, why is your link down ? node reboot ? if not, you have clearly a problem with nic , the cable, or the switch port[/spoiler]
  6. spirit

    Corosync link flapping with 3 nodes

    corosync mtu is always lower than real mtu. in my production, I have also 1397 pmtud with 1500 mtu on nic Feb 19 11:05:20 corosync[23618]: [KNET ] pmtud: PMTUD link change for host: 4 link: 0 from 469 to 1397
  7. spirit

    NAS iSCSI LUN and LVM-Shared on top - bad IO while having VM delete ongoing

    the current code is my $secure_delete_cmd = sub { my ($lvmpath) = @_; my $stepsize = $scfg->{'saferemove-stepsize'} // 32; $stepsize = $stepsize * 1024 * 1024; my $bdev = abs_path($lvmpath); my $sysdir = undef; if ($bdev && $bdev =~...
  8. spirit

    Ceph - VM with high IO wait

    Hi Tchaikov, I think that the user setup is hyperconverged with proxmox/ceph on the 3 nodes. So, I think that the rbd client is able to handle it without hook . could you confirm this ? (I have seen other proxmox users doing it in hyperconverged, and it seem to works fine) I would like to...
  9. spirit

    Corosync link flapping with 3 nodes

    it's look like to nic of the 3th is going down/up or flapping. nic driver bug ? maybe bad cable ? do you have any kernel log on the 3th node ? #dmesg ? maybe also try without bonding/lacp with 2 corosync links
  10. spirit

    Proxmox/Ceph - Disable OSD rebalancing

    I think what you want is to simply enable noout flag or set mon_osd_down_out_interval to 1hour instead 10min
  11. spirit

    ZFS mirror on 2x Crucial T705 (PCIe 5.0) causing txg_sync hangs under write load – no NVMe errors in dmesg

    10year old ceph blog, also apply for zfs https://ceph.io/en/news/blog/2014/ceph-how-to-test-if-your-ssd-is-suitable-as-a-journal-device/ https://www.sebastien-han.fr/blog/2014/10/10/ceph-how-to-test-if-your-ssd-is-suitable-as-a-journal-device/ don't expect any good performance with consumer...
  12. spirit

    Cluster retransmit issues

    About spanning-tree, you should really disable it on your physical switch port of for your proxmox nodes. a spanning tree convergence can happen on host reboot and broke the whole cluster for some second. you don't need change knet_mtu, it's auto-compute by corosync. it could be a bug with the...
  13. spirit

    Ceph - VM with high IO wait

    Strange that you also have high memory pressure "PSI some memory". do you have enable numa option on the vm ? you can also look at host numa stat # apt install numactl # numstat and look if you don't have a lot of "numa_miss" vs "numa_hit" on rbd side, you can also give a try to krbd vs...
  14. spirit

    Cluster retransmit issues

    can you send corosync log of each node ? (journalctl -u corosync). is the nic for corosync link dedicated ? or do you have vm,storage,backup,...running on it too ? (no bandwidth saturation ? ) no spanning tree on the network ? do you use bonding or not ?
  15. spirit

    Interest in VPP (Vector Packet Processing) as a dataplane option for Proxmox

    firewall=1 is create a linux bridge fwbr interface, so it's not usable here. Implementing the whole firewall code in vpp is another thing. (and currently proxmox code don't have any easy plugin code to implement different firewall)
  16. spirit

    How to disable the bridge level firewall in PVE 9.1.1

    So, why do you want to use pve-firewall ? (I mean, disable pve-firewall service or uncheck firewall checkbox on the vms) I'll try to look at proxmox-firewall code, but it shouldn't be needed
  17. spirit

    Interest in VPP (Vector Packet Processing) as a dataplane option for Proxmox

    maybe the best way is to ask to the dev mailing list pve-devel@lists.proxmox.com. (I'm pretty sure that some users could be interested for routers vm appliance) the basic dev doc for patch submission is here: https://pve.proxmox.com/wiki/Developer_Documentation does it expose a vswitch ? if...
  18. spirit

    How to disable the bridge level firewall in PVE 9.1.1

    This is needed if you want to use iptables (used by pve-firewall) to have ip rules at bridge level. why do you want to disable them ? Alternatively, they shouldn't be needed by the new nftables based firewall (proxmox-firewall services), as nftables is able to handle it without tricks at...
  19. spirit

    Interest in VPP (Vector Packet Processing) as a dataplane option for Proxmox

    Hi, I don't remember, but does it work with virtio-net ? I thinked it need vhost-user-net (that is not implement in proxmox currently )
  20. spirit

    rp_filter changes in PVE 9

    mmm, this seem to be a change in debian13: https://www.debian.org/releases/trixie/release-notes/issues.html#etc-sysctl-conf-is-no-longer-honored In Debian 13, systemd-sysctl no longer reads <span>/etc/sysctl.conf</span>. The package linux-sysctl-defaults ships...