[pve-devel] [PATCH V2 pve-network 1/1] bridge-disable-mac-learning : use $opts for tap_plug

Signed-off-by: Alexandre Derumier --- PVE/Network/SDN/Zones.pm| 5 +++-- PVE/Network/SDN/Zones/Plugin.pm | 4 +++- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/PVE/Network/SDN/Zones.pm b/PVE/Network/SDN/Zones.pm index 492defd..f8e40b1 100644 ---

[pve-devel] [PATCH qemu-server/container/network 0/3] implement bridge disable learning

Hi, This is a resent of missing patches to implement bridge disable learning in 7.2 release note https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.2 It has been announced that bridge-disable-mac-learning could be disable in /etc/network/interfaces, but the qemu-server/lxc plugging patches has

[pve-devel] [PATCH V3 qemu-server 3/3] migration : add del_nets_bridge_fdb

at the end of a live migration, we need to remove old mac entries on source host (vm is not yet stopped), before resume vm on target host Signed-off-by: Alexandre Derumier --- PVE/QemuMigrate.pm| 1 + PVE/QemuServer.pm | 20

[pve-devel] [PATCH V3 qemu-server 1/3] tap_plug: add support for bridge disable learning

This disabling mac learning && unicast flood for the tap interface for vmstart, we don't add mac directly to fdb. We set it latter if it's a migration or a fresh start. for nic hotplug, we directly add mac to fdb Signed-off-by: Alexandre Derumier --- PVE/QemuServer.pm | 8 +++-

[pve-devel] [PATCH V3 qemu-server 2/3] vm_start/vm_resume : add_nets_bridge_fdb

on vm start (no live migration), we can simply add mac address in fdb. In case of a live migration, we add the mac address just before the resume. Signed-off-by: Alexandre Derumier --- PVE/QemuServer.pm | 25 +++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git

[pve-devel] [PATCH V3 pve-container 1/1] net : add support for bridge disable mac learning

Signed-off-by: Alexandre Derumier --- src/PVE/LXC.pm | 16 ++-- src/lxcnetaddbr | 7 ++- 2 files changed, 20 insertions(+), 3 deletions(-) diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm index fe63087..f6501bb 100644 --- a/src/PVE/LXC.pm +++ b/src/PVE/LXC.pm @@ -949,8 +949,14 @@

Re: [pve-devel] proxmox French days conference feedback

Hi Thomas, Sorry I totally miss your reponse ! >> - a drs feature like vmware for vm balancing >> (I'm still working on it, I'll try to have a working after this summer. >> I still need vm pressure stats pending patches apply first  > > I'd really like to more actively work on this from our

[pve-devel] [PATCH firewall] fix invalid vmfw config being interpreted as enabled

MAC filter was enabled as long as the VM firewall config existed even with an invalid config. With this change the check now matches the one for CTs. Signed-off-by: Mira Limbeck --- src/PVE/Firewall.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/PVE/Firewall.pm

[pve-devel] [PATCH V2 qemu-server 2/2] tests: add virtio-mem tests

Signed-off-by: Alexandre Derumier --- test/cfg2cmd/simple-virtio-mem-big.conf | 12 + test/cfg2cmd/simple-virtio-mem-big.conf.cmd | 59 + test/cfg2cmd/simple-virtio-mem.conf | 13 + test/cfg2cmd/simple-virtio-mem.conf.cmd | 31 +++ 4 files

[pve-devel] [PATCH V2 qemu-server 0/2] add virtio-mem support

This patch add virtio-mem support, through a new maxmemory option. a 4GB static memory is needed for DMA+boot memory, as this memory is almost always un-unpluggeable. 1 virtio-mem pci device is setup for each numa node on pci.4 bridge virtio-mem use a fixed blocksize with 32k max blocksize, so

[pve-devel] [PATCH V2 qemu-server 1/2] add virtio-mem support

This patch add virtio-mem support, through a new maxmemory option. a 4GB static memory is needed for DMA+boot memory, as this memory is almost always un-unpluggeable. 1 virtio-mem pci device is setup for each numa node on pci.4 bridge virtio-mem use a fixed blocksize with 32k max blocksize, so

[pve-devel] [PATCH pve-network 3/3] frr: config : add exit on router && routemaps.

added recently in last frr releases, just to be sure to no break on future releases Signed-off-by: Alexandre Derumier --- PVE/Network/SDN/Controllers/EvpnPlugin.pm| 5 + test/zones/evpn/advertise_subnets/expected_controller_config | 4

[pve-devel] [PATCH pve-network 1/3] frr: update config frrversion to 8.2.2

Signed-off-by: Alexandre Derumier --- PVE/Network/SDN/Controllers/EvpnPlugin.pm | 2 +- test/zones/evpn/advertise_subnets/expected_controller_config| 2 +- .../evpn/disable_arp_nd_suppression/expected_controller_config | 2 +-

[pve-devel] [PATCH pve-network 0/3] evpn improvment

This patches series cleanup some frr 8.2 config file format, add support for routemaps, and also improve custom local configuration merging. Alexandre Derumier (3): frr: update config frrversion to 8.2.2 frr: add a local config parser and merge with generated config frr: config : add exit

[pve-devel] [PATCH pve-network 2/3] frr: add a local config parser and merge with generated config

some users with very specific config want to be able to add custom local config and merge it with generated config Signed-off-by: Alexandre Derumier --- PVE/Network/SDN/Controllers/EvpnPlugin.pm | 95 --- 1 file changed, 86 insertions(+), 9 deletions(-) diff --git

Re: [pve-devel] [PATCH] Update cpu.weight default to match documented default

Am 24.08.22 um 01:56 schrieb Matt Corallo: > > > On 8/19/22 6:08 AM, Fiona Ebner wrote: >> Hi, >> >> On 16.08.22 05:49, Matt Corallo wrote: >>> Proxmox documentation describes the default CPU weight as 1024 in >>> numerous places. However, when unset, the Linux default CGROUP >>> weight is 100.