Browse Source

Update proxmox-ve.md

Nordstrand 2 years ago
parent
commit
ad811325dc
1 changed files with 8 additions and 4 deletions
  1. 8 4
      virt-cont/proxmox-ve.md

+ 8 - 4
virt-cont/proxmox-ve.md

@@ -42,10 +42,14 @@ PVE-specific instructions:
     1. Create `/etc/apt/sources.list.d/pve-no-subscription.list` containing `deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription` to enable the no-subscription repo.
     1. Run a full upgrade: `apt update && apt full-upgrade`
 1. Update network config:
-    1. (Note) Do NOT manually modify the configs for DNS, NTP, IPTables, etc. However, the network config (`/etc/network/interfaces`) and PVE configs _may_ be manually modified, but the GUI or API is still recommended.
-    1. (Note) For complicated VLAN setups, you want to use OVS stuff instead of plain Linux stuff. Plain Linux stuff (the way PVE uses it) may break for certain setups where e.g. PVE has a VLAN L3 interface on the same bridge as a VM is connected to the same VLAN.
-    1. (Note) OVS bonds: Use mode "LACP (balance-tcp)" and manually specify OVS option `lacp-time=fast`.
-    1. Update network config: Use the web GUI.
+    1. (Note) Do NOT manually modify the configs for DNS, NTP, IPTables, etc. The network config (`/etc/network/interfaces`) and PVE configs _may_ however be manually modified, but the GUI or API is still recommended.
+    1. (Note) Consider using Open vSwitch (OVS):
+        - Plain Linux stuff (the way PVE uses it at least) may break for certain setups where e.g. PVE has a VLAN L3 interface on the same bridge as a VM has one.
+        - If using VLANs and an LACP link:
+            1. Create the OVS bridge (`vmbr<N>`). When adding tagged or untagged VM interfaces later, use this bridge.
+            1. Create the OVS bond (LACP) (`bond<N>`). Use the created bridge as the "OVS bridge" and the physical interfaces as the "slaves". Use mode "LACP (balance-tcp)" and add the OVS option `other_config:lacp-time=fast`.
+            1. Create the OVS IntPort (VLAN interface) (`vlan<VID>`), which PVE will use to access the network. Use the OVS bridge and specify the VLAN ID. Set the IP addresses for PVE here.
+    1. Update network config: Use the web GUI. 
 1. Update MOTD:
     1. Disable the special PVE banner: `systemctl disable --now pvebanner.service`
     1. Clear or update `/etc/issue` and `/etc/motd`.