Just upgraded to Proxmox 7.0.11 and found that none of my VMs would work due to networking issues preventing connection to my network shares. I have two dual port NICS with LACP bonds set up. One used for NFS connections (VM and ISO storage), one for virtual server comms. On Proxmox 6.4 the two NICs interfaces could operate with bonds setup even with autostart enabled.
So on Proxmox 6.4 this network setup worked:
After upgrading to Proxmox 7.0.11, I had to remove the 'auto' lines for enp35s0f0/enp35s0f1 and enp4s0f0/enp4s0f1 for the bonds to work.
e.g
Now. If I edit the network settings inside the Web GUI. Not matter what the setting of the Autostart flag, it will reenable Autostart on all those interfaces again.
The Autostart flag is ignored when you turn it off and after you hit OK it turns ON Autostart on ALL interfaces.
This is the state of my network interfaces before I edit one of the network adapters:
Now if I edit an interface:
and hit OK. I get this:
As you can see. Autostart is now turned on on all the interfaces. Which, of course, will break stuff on reboot.
Here's what it'll do:
So on Proxmox 6.4 this network setup worked:
auto lo
iface lo inet loopback
iface enp6s0 inet manual
auto enp35s0f0
iface enp35s0f0 inet manual
auto enp35s0f1
iface enp35s0f1 inet manual
auto enp4s0f0
iface enp4s0f0 inet manual
auto enp4s0f1
iface enp4s0f1 inet manual
auto bond0
iface bond0 inet manual
bond-slaves enp35s0f0 enp35s0f1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
auto bond1
iface bond1 inet static
address xxx.xx.xxx.xxx/24
bond-slaves enp4s0f0 enp4s0f1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
auto vmbr0
iface vmbr0 inet static
address xxx.xx.x.xxx/24
gateway xxx.xx.x.x
bridge-ports enp6s0
bridge-stp off
bridge-fd 0
auto vmbr1
iface vmbr1 inet manual
bridge-ports bond0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
After upgrading to Proxmox 7.0.11, I had to remove the 'auto' lines for enp35s0f0/enp35s0f1 and enp4s0f0/enp4s0f1 for the bonds to work.
e.g
auto lo
iface lo inet loopback
iface enp6s0 inet manual
iface enp35s0f0 inet manual
iface enp35s0f1 inet manual
iface enp4s0f0 inet manual
iface enp4s0f1 inet manual
auto bond0
iface bond0 inet manual
bond-slaves enp35s0f0 enp35s0f1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
auto bond1
iface bond1 inet static
address xxx.xx.xxx.xxx/24
bond-slaves enp4s0f0 enp4s0f1
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer2
auto vmbr0
iface vmbr0 inet static
address xxx.xx.x.xxx/24
gateway xxx.xx.x.x
bridge-ports enp6s0
bridge-stp off
bridge-fd 0
auto vmbr1
iface vmbr1 inet manual
bridge-ports bond0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094
Now. If I edit the network settings inside the Web GUI. Not matter what the setting of the Autostart flag, it will reenable Autostart on all those interfaces again.
The Autostart flag is ignored when you turn it off and after you hit OK it turns ON Autostart on ALL interfaces.
This is the state of my network interfaces before I edit one of the network adapters:
Now if I edit an interface:
and hit OK. I get this:
As you can see. Autostart is now turned on on all the interfaces. Which, of course, will break stuff on reboot.
Here's what it'll do:
Pending changes (Either reboot or use 'Apply Configuration' (needs ifupdown2) to activate)
--- /etc/network/interfaces 2021-08-21 14:26:42.434978625 +0100
+++ /etc/network/interfaces.new 2021-08-21 15:19:31.874790513 +0100
@@ -14,15 +14,19 @@
iface enp6s0 inet manual
+auto enp35s0f0
iface enp35s0f0 inet manual
-#Don't need autostart
+#Added a comment
+auto enp35s0f1
iface enp35s0f1 inet manual
#Don't need autostart
+auto enp4s0f0
iface enp4s0f0 inet manual
#Don't need autostart
+auto enp4s0f1
iface enp4s0f1 inet manual
#Don't need autostart
