Search results

Same here, 4+ days uptime without crash with 6.8.4-3-pve now. Seems to fix one of the issues.

Logs in this post further back. No, not yet.

Yes, we use encryption on our OSD and I remember seeing storage/dm-crypt related traces!

It only crashes on the 3 ceph nodes with additional nvme devices and Mellanox Connect-X3 - the compute nodes do not crash. Same boards, same CPU Gen, all X10DRU-i+ and E5-26xx v4.

Actually not true. it still crashes here with that. Supermicro X10DRU-i+ and Intel E5-26xx v4.

My X540-AT2 based X10DRU-i+ run fine, when they do not have NVME storage and no Connect-X3 and no ceph-osd. So I do not see the Intel NIC as the culprit.

Ich habe hier 11 Kisten mit Supermicro X10DRU-i+ und BIOS 3.5. CPUs sind E5-2620 v4 in den 3 Ceph nodes und E5-2667 v4 und E5-2683 v4 in den Compute Nodes. Ceph Nodes haben NVME Storage und Connect-X3 Karten, Compute Nodes nur die onboard X540-AT2. 6.8.4 funktioniert auf den Compute Nodes ohne...

Probiers mal mit Kernel 6.5.13.

Still crashes with intel_iommu=off and BIOS updated to 3.5. Back to 6.5.13 for now.

Also crashes here with 6.8.4 and not with 6.5.13: Supermicro X10DRU-i+, Bios 3.4 E5-2620 v4 01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit X540-AT2 (rev 01) 88:00.0...

Same here, sometimes the opcode bytes are listed though: [Mon Jul 17 05:04:28 2023] pverados[740828]: segfault at 55a4a3d5d030 ip 000055a4a3d5d030 sp 00007ffecd408178 error 14 in perl[55a4a3d31000+195000] likely on CPU 1 (core 2, socket 0) [Mon Jul 17 05:04:28 2023] Code: Unable to access...

I am seeing the same issue here after the upgrade of the OPNsense to 22.1.

Could you please elaborate a bit? How do you configure the VLAN filter? I am trying something similar but with Intel X553, ixgbe (linux/proxmox) and iavf (opnsense). So far I have not succeeded in getting a trunk port to work in opnsense. The multicast issue for carp can be solved with...

actually, to my understanding you don't. you can run all vxlan-ids in the same multicast group. it is counterproductive to spawn multicast groups per vxlan. Default for linux is max. 20 igmp memberships... net.ipv4.igmp_max_memberships = 20 yes, i had a look at bgp-evpn. currently i am...

I have some thoughts regarding the SDN VXLAN implementation. The VXLAN interface is configured with vxlan_remoteip <peerips>. To my understanding this means that BUM traffic is replicated from one node to all others. This has implications for scaling. Another approach would be to use a...

Did you actually apply that config? pvesh set /cluster/sdn ifreload -a

I guess ifupdown2:3.0.0-1+pve3 contains the fix for vlans on vxlan?

@spirit indeed, with this patched version of ifupdown2 it works as expected! \o/ Thanks!

I can confirm that bridge-access 1 makes this work for vlanaware 1 \o/ but bridge-access 1 obviously makes only vlan=1 work...