From: Hannes Laimer <h.laimer@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-manager v3 16/17] sdn: bring up the DHCP backends at boot before the guests start
Date: Wed, 21 Oct 2026 09:17:57 +0200 [thread overview]
Message-ID: <af7fbfcb-8eae-4dcc-b592-ece03d5625d6@proxmox.com> (raw)
In-Reply-To: <d3f3f9b1-9bd6-4699-aa67-68e173716edd@proxmox.com>
On 2026-10-20 15:22, Stefan Hanreich wrote:
> On 10/20/26 10:03 AM, Hannes Laimer wrote:
>> The eBPF DHCP responder keeps its programs and maps pinned in bpffs,
>> so they are gone after a reboot. The SDN commit helper now brings the
>> DHCP backends back up on every boot, not only when it has changes to
>> commit.
>>
>> The helper runs before the node and HA start the guests at boot.
>> Otherwise the first guest interface plug loads the responder with a
>> full pass, which holds the responder's lock exclusively. A guest
>> starting meanwhile waits for that lock. One that waits too long comes
>> up without the responder on its interface.
>>
>> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
>> ---
>> bin/pve-sdn-commit | 3 +++
>> services/pve-sdn-commit.service | 1 +
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/bin/pve-sdn-commit b/bin/pve-sdn-commit
>> index aa7e9b29..ed2d6935 100644
>> --- a/bin/pve-sdn-commit
>> +++ b/bin/pve-sdn-commit
>> @@ -96,6 +96,9 @@ sub sdn_changed {
>> return fabrics_changed();
>> }
>>
>> +# the dhcp backends bring back what a reboot took, pending changes or not
>> +PVE::Network::SDN::Dhcp::boot();
>
> Add some form of log message here. I've tested this and it worked but I'd
> like at least some form of confirmation that this ran successfully?
>
reasonable :) will add in v4
>> +
>> if (!sdn_changed()) {
>> print "No changes to SDN configuration detected, skipping reload\n";
>> exit 0;
>> diff --git a/services/pve-sdn-commit.service b/services/pve-sdn-commit.service
>> index ff723725..825926be 100644
>> --- a/services/pve-sdn-commit.service
>> +++ b/services/pve-sdn-commit.service
>> @@ -3,6 +3,7 @@ Description=Commit Proxmox VE SDN changes
>> DefaultDependencies=no
>> Wants=pve-cluster.service network.target
>> After=frr.service network.target corosync.service
>> +Before=pve-guests.service pve-ha-lrm.service
>>
>> [Service]
>> ExecStart=/usr/share/pve-manager/helpers/pve-sdn-commit
>
>
>
>
>
next prev parent reply other threads:[~2026-10-21 7:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 7:59 [PATCH container/docs/manager/network/proxmox{-ebpf,-perl-rs}/qemu-server v3 00/17] sdn: implement DHCP for all zones using eBPF Hannes Laimer
2026-10-20 7:59 ` [PATCH proxmox-ebpf v3 01/17] dhcp: add the per-tap DHCPv4 responder program Hannes Laimer
2026-10-20 7:59 ` [PATCH proxmox-ebpf v3 02/17] dhcp: add the subsystem that loads the responder and keeps its records Hannes Laimer
2026-10-20 13:09 ` Stefan Hanreich
2026-10-21 7:09 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH proxmox-perl-rs v3 03/17] pve-rs: sdn: add bindings for the eBPF DHCP responder Hannes Laimer
2026-10-20 13:10 ` Stefan Hanreich
2026-10-21 7:32 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 04/17] sdn: dhcp: replace a stale dnsmasq reservation instead of dropping it Hannes Laimer
2026-10-20 13:15 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 05/17] sdn: dhcp: update reservations when ip mappings change Hannes Laimer
2026-10-20 13:42 ` Stefan Hanreich
2026-10-21 7:21 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 06/17] sdn: ipam: key the MAC cache by lower-case MAC, stop caching misses Hannes Laimer
2026-10-20 13:10 ` Stefan Hanreich
2026-10-21 6:17 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 07/17] sdn: dhcp: make the lease time configurable per subnet Hannes Laimer
2026-10-20 13:17 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 08/17] sdn: dhcp: require a backend only if a zone on this node uses it Hannes Laimer
2026-10-20 13:17 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 09/17] sdn: dhcp: add an eBPF backend answering on each guest interface Hannes Laimer
2026-10-20 13:10 ` Stefan Hanreich
2026-10-21 6:16 ` Hannes Laimer
2026-10-20 7:59 ` [PATCH pve-network v3 10/17] sdn: zones: report interface plugs and unplugs to the DHCP backends Hannes Laimer
2026-10-20 13:17 ` Stefan Hanreich
2026-10-20 7:59 ` [PATCH pve-network v3 11/17] sdn: dhcp: push IP mapping edits to the guest's node Hannes Laimer
2026-10-20 13:09 ` Stefan Hanreich
2026-10-21 6:44 ` Hannes Laimer
2026-10-20 8:00 ` [PATCH pve-network v3 12/17] sdn: zones: allow the ebpf DHCP backend on every zone type Hannes Laimer
2026-10-20 8:00 ` [PATCH qemu-server v3 13/17] network: sdn: keep the DHCP backends current on guest NICs Hannes Laimer
2026-10-20 13:38 ` Stefan Hanreich
2026-10-20 8:00 ` [PATCH pve-container v3 14/17] net: report NIC plugs and removals to the SDN DHCP backends Hannes Laimer
2026-10-20 13:36 ` Stefan Hanreich
2026-10-21 7:29 ` Hannes Laimer
2026-10-20 8:00 ` [PATCH pve-manager v3 15/17] ui: sdn: add zone DHCP backend selector and subnet DHCP options Hannes Laimer
2026-10-20 13:19 ` Stefan Hanreich
2026-10-20 8:00 ` [PATCH pve-manager v3 16/17] sdn: bring up the DHCP backends at boot before the guests start Hannes Laimer
2026-10-20 13:21 ` Stefan Hanreich
2026-10-21 7:17 ` Hannes Laimer [this message]
2026-10-20 8:00 ` [PATCH pve-docs v3 17/17] sdn: dhcp: add eBPF backend section Hannes Laimer
2026-10-20 13:11 ` [PATCH container/docs/manager/network/proxmox{-ebpf,-perl-rs}/qemu-server v3 00/17] sdn: implement DHCP for all zones using eBPF Stefan Hanreich
2026-10-21 7:35 ` Hannes Laimer
2026-10-21 8:46 ` superseded: " Hannes Laimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af7fbfcb-8eae-4dcc-b592-ece03d5625d6@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.