Proxmox imports OVA/OVF natively now through a storage with the "import"
content type, or qm importovf. The built-in path also handles per-storage disk
format conversion, which neither script did.
Recorded the known bugs in each header rather than fixing them, since nothing
will run these again: import-ova-pve.py imports every VMDK but only attaches
disk-0, leaving multi-disk appliances partly orphaned, and assumes a
vm-<vmid>-disk-N name that not every storage type uses;
import-ova-to-proxmox.sh passes --format qcow2 unconditionally, which fails on
ZFS and LVM-thin.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
It was meant to restart the NUT driver from a udev RUN+= when the UPS
re-enumerates on USB, but was never wired up: 50-nut-ups.rules only sets MODE
and GROUP.
systemd already covers the case. nut-driver@ups.service is Restart=always
with RestartUSec=15s, so the driver is retried indefinitely and reattaches to
a new device node unaided.
It would also not have worked reliably. systemd-udevd kills RUN+= handlers
still alive when the event completes, so the backgrounded subshell could be
killed mid-sleep, and upsdrvctl would run the driver outside the unit's
supervision, competing with systemd's own restarts.
Kept with a header recording the rule-based alternative if faster recovery is
ever wanted.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tailscale's UDP GRO forwarding tuning applies to the machine running
tailscaled. That is VM 100 (ts-subnet-rtr), a KVM guest with its own kernel
and netdevs, so ethtool on the Proxmox host cannot affect its forwarding
path. Host-side tuning would only have been the right lever for a tailscaled
running in an LXC container, which shares the host kernel.
The interfaces were wrong in any case. VM 100 is on vmbr7, backed by
enp4s0f7np7. vmbr0 is backed by enp4s0f0np0 and carries unrelated guests, and
enp4s1f12np12 is the host's own routing NIC and not a bridge port at all.
It never ran: the header says to run it from root's crontab, and root has no
crontab. Both offloads were still off on every interface it named.
Kept with a header recording where the tuning actually belongs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Docker is not installed on pet630, so neither of these can run there:
- docker-idrac.sh is the container-based alternative to the ipmi-fancontrol
scripts, which remain in service.
- webnut-docker/ is the web UI for the NUT daemon. NUT itself is still
running on the host; only this front end is retired.
The gitignored .env moves with the compose file and is still excluded at the
new path.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Checked against the live host. None of these are in service:
- sriov-enp4s0.service and set-ixgbe-vfmacs-enp4s0.sh target enp4s0f1np1,
which no longer exists; sriov_numvfs is 0 on every port and the unit was
never installed.
- nic-performance-tweaks.service was never installed either, though its
interfaces do still exist, so it would work if reinstated.
- vm-watchdog.sh watches VMID 2801 "pfsense", which no longer exists.
- lxc-watchdog.sh still carries the upstream example targets: CT 100 and
CT 101 on 192.168.31.0/24, a subnet that is not in use.
Neither watchdog is scheduled; there is no root crontab.
The watchdog config moves to unused/conf/ alongside them, so the scripts
resolve it unchanged from their new location.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
sriov-enp4s0.service allocates VFs on the ixgbe ports at boot and applies
persistent VF MACs via set-ixgbe-vfmacs-enp4s0.sh, so guests keep stable
addresses across host reboots. The VF MAC assignments are currently all
commented out.
nic-performance-tweaks.service raises ring buffers and txqueuelen on the
uplinks and vmbr0.
unused/ holds the equivalent pair for the retired enp130s0 adapter.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ergosteurandClaude Opus 5