Search results

Small 3 node cluster. ZFS on root. Ceph 18.2. Have x553 SFP+ based networking and no issues so far.

Thanks @shodan. Used as well. a couple optional changes I made was to set a static IP for the lan ipaddr and if you stick with DHCP I added the ifconfig command as the last step to show the IP at the end of the script. added the 2 variables below to the top section for those wanting a...

With that additional info I would amend my suggestion: # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read its network # configuration from sourced files, so do not attempt to move any of # the PVE managed interfaces...

Are eno1-2 physically connected to a switch? If so, will you bond them together at the switch and in Proxmox or leave them bridged as in the example attachment?

If you give a LXC/VM a network device (no vlan tagged there) vmbr2.205 or vmbr2.215 do they have network connectivity on those vlans as expected? Is my assumption that Eth01 and Eth02 are connected to a physical switch correct? If so, have you double-checked the respective switch ports vlan...

Try the below for a start. Are you not intending to use any of the other 3 ports of this card, eno2-4? Example: Use VLAN 5 for the Proxmox VE management IP with VLAN aware Linux bridge https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_vlan_on_the_host 3 options to accomplish what I think...

vlan 1 (0 too for diff reasons) are special cases and linux bridges and/or some switches do not work well using it tagged. one of the reasons bridge-vids 2-4094 is the the default and I assume you manually edited to bridge-vids 0-4094 . Suggest moving to the way Proxmox documentation states...

So to be clear this is/was a main linux kernel ixgbe regression affecting all distributions dating back to kernel 6.1. It was only reverted in 6.9 and backported to LTS Kernels 6.6 and 6.1 in May 2024. So Proxmox (actually Ubuntu) is only 2-3 months behind on back porting this fix to 6.8. See...

You should not need to build the ixgbe OOT driver with 6.8.12-1, it should just work out of the box. use proxmox-boot-tool kernel pin 6.8.12-1-pve --next-boot to force trial the new kernel on the next boot only. I am curious if you have pinned the old 5.15 kernel? and the DKMS error message...

So do you want the #external bridge and servers to both be on vlan 10 Using vmbr0/eno2? vmbr0.10 = vlan10 using vlan-raw device vmbr0 If that is what you want try: auto External iface External inet inet static address 10.10.0.4/24 gateway 10.10.0.1 bridge-ports vmbr0.10...

What are you trying to do here? to what bridge are you connecting the VM's? Does the Proxmox host have appropriate internet access? auto lo iface lo inet loopback iface eno2 inet manual auto vmbr0 iface vmbr0 inet static address 192.168.0.74/29 gateway 192.168.0.73...

So first vmbr0.10 example you have set up vlan10/vmbr0.10 in three different ways. 1 of them is just to give a static address to proxmox of 10.10.0.4, so all good there. The last 2 include iface External inet static , but no static address. Use iface External inet manual instead. I would keep...

Proxmox released proxmox-kernel-signed-6.8.12-1 to the no-subscription repository, which sources Ubuntu-6.8.0-43.43 (where ubuntu finally reverts the ixgbe 553 breakage from back in Linux Kernel 6.1). Try it out, installed and works after reboot without the OOT intel IXGBE installed for me...

After a couple of years Ubuntu seems to have recently reverted the Linux kernel regression causing this issue dating back to kernel 6.1 AND Proxmox may finally pick up the fix in an upcoming kernel. https://lists.proxmox.com/pipermail/pve-devel/2024-August/065041.html

Thanks, hopefully, this is a universal way forward. Copied your post to the bug report for this issue: Bug 5103 - intel x553 SFP+ ixgbe does not link up on pve8 or pve8.1

The naming structure changed somewhere after the switch to the early Linux 6 kernels Promox 7 or so, which this machine locked to linux 5.3 skipped. Not sure about the grub directory errors, but believe I have seen the same. When you're booting do you see GRUB or systemd-boot...

In order to get dkms automatically working again with ixgbe/5.20.10 and kernel 6.8.8-* updates, obviously need to replace 5.20.10 in the above steps, but also I had to rm -rf /var/lib/dkms/ixgbe (before going through the last 3 commands starting with sudo dkms add ixgbe/5.2.10) or DKMS would...

I should have mentioned, be prepared to potentially have some of your network interface names changed once booted into the latest kernel. If networking is off or not working, ip a and compare the interface names with what you have with the older naming conventions in /etc/network/interfaces...

at some point 5.3.10-1-pve was pinned given the proxmox-boot-tool kernel list output shown. proxmox-boot-tool kernel unpin and reboot will undo this or if you want to be cautious start with proxmox-boot-tool kernel unpin --next-boot and reboot for single use trial. If all good after reboot...

To start you may want to consider editing your /etc/network/interfaces with the changes below: auto vmbr0 iface vmbr0 inet static address 192.168.5.150/24 bridge-ports enp2s0 bridge-stp off bridge-fd 0 bridge-vlan-aware yes bridge-vids 2-4094 auto vmbr1 iface vmbr1...