Search results

What about the openvswitch-switch instead of linux bridge functionality?

Problem comes about when I have VLAN Trunking enabled on the switch port but either proxmox kernel tries to allocate all 4K vlans and crashes the NIC. But setting switchport to access mode never causes the crash as only 1 vlan gets passed through. This seems like a Ubuntu Kernel Regression

I also have this issue with 2 up-2-date Dell R720's in a cluster. Occasionally some VM's would fail with that error This only happens to certain VM's and not all Windows VM's Running Xeon E5-2640 and E5-2643's in a cluster with CEPH I will try applying that kvm.tdp_mmu=N Option and see if that...

I have also come across this issue and it seems that deleting that file fixes all of the issues accordingly as stated above. I was trying to wrap my head around this when my proxmox on OVH decided to Stall on boot because of wait for link up file causing this.

I have figured out the OVH Proxmox Template has an addition file that wait's for link up in /etc/network/if-pre-up.d/wait_for_link_up which causes this boot process to stall on creating additional Bridge adapters and bringing them online.

I don't know what this issue is but it seems like after a clean install of Proxmox VE 6.4-6 has issues with ifupdown2 on OVH and I cannot seem to get the interfaces to work even after uninstall their cloud-init and resovconf packages. The SRV Networking (ifreload -a) issue with the invalid use...