I could not find _any_ reference to it in current checkouts of ~every
Proxmox repository.
AFAICT this was copied from pve-installer in pve-installer commit
f0583fd4e ("copied country.pl form pve-manager")
in 2017 and simply never dropped here afterwards, so it's an unused
leftover.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
Link: https://lore.proxmox.com/20250828103621.936206-1-c.heiss@proxmox.com
Without this a `udevadm verify` execution warns about:
70-virtual-function-pinning.rules:1 style: whitespace after comma is expected.
70-virtual-function-pinning.rules:1 style: whitespace after comma is expected.
70-virtual-function-pinning.rules:1 style: whitespace after comma is expected.
70-virtual-function-pinning.rules: udev rules have style issues.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commmit adds a udev rule that triggers for every network device
that gets added. It checks if the network device is a VF and if the
parent device is pinned. If it is pinned, then generate a new name for
the VF which consists of the pinned name of the parent device, as well
as the index of the VF.
It relies on the network device driver exposing the information via
sysfs, which was the case in my tests for mlx5_core, igb and bnxt_en.
Specifically it checks if a device is a virtual function by checking
for the existence of:
/sys/class/net/<iface>/device/physfn
It then follows that symlink and infers the vf index by looking at the
virtfnX symlinks in the folder above.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
Link: https://lore.proxmox.com/20250722145223.351778-2-s.hanreich@proxmox.com
using the new top-level `make tidy` target, which calls perltidy via
our wrapper to enforce the desired style as closely as possible.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Include the additional parameter to set the `change-detection-mode`
for backup jobs with Proxmox Backup Server target as node wide
configuration, including possible variants to be set.
Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
because otherwise we need to house *all* defaults, like the interface
naming policy ones, too.
This can be fine for one release, but easily overlooked if those, or
other important fall-back defaults change.
A user can now also easier override this, e.g., by simply adding a
drop-in file in the respective /etc path.
Fixes failure to rename network names to "predictable" names on boot
as reported in the forum:
https://forum.proxmox.com/threads/135635/page-6#post-606130
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
since debian 11, systemd is changing behaviour of MAC address of
bridge, but also bond, where the mac is generated randomly instead
inherit from the first slave.
We tried to fix that with ifupdown2, but that seems to produce some
regressions and independent of that there was still another problem.
Namely, if a bridge don't have any slaves, systemd is keeping bridge
offline.
https://www.justinsteven.com/posts/2023/03/26/virtualbox-bridge-ports-none-no-carrier-debian-11/
That mean that a dhcp daemon like kea can't bind on a standalone
bridge (used for s-nat for example), until a tap interface is started.
So, set up a systemd link config to disable the systemd mac policy by
default (this don't break already fixed ifupdown2 mac).
Funnily CentOS && Fedora also disable it already:
https://fedoraproject.org/wiki/Changes/MAC_Address_Policy_nonec895351950/0028-udev-net-setup-link-change-the-default-MACAddressPol.patch (L43)
Before this patch:
```
~ ip a sh dev vmbr1
vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 10
```
After this patch:
```
~ ip a sh dev vmbr1
vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
```
Signed-off-by: Alexandre Derumier <alexandre.derumier@groupe-cyllene.com>
[ TL: move to /usr/lib/.. where distro files belong and add comment ]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
configuring pbs-entries-max can avoid failing backups due to a high
amount of files in folders where a folder exclusion is not possible
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
Also generalizes the way vzdump property strings are handled for jobs.
Something similar could be done in VZDump.pm, but there the maxfiles
and prune-backups settings are currently coupled, so a dedicated
parse_performance() is used instead. Can be changed once maxfiles is
dropped.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Instead of marking all pve-kernel-.* packages as NeverAutoRemove we compile
a list of specific versions to keep.
This functionality is added in the proxmox-ve package (along with the config
for booting kernels with systemd-boot).
