Recent content by Shannon Barber

Here's the patch ... diff --git a/src/PVE/LXC/Setup/Base.pm b/src/PVE/LXC/Setup/Base.pm --- a/src/PVE/LXC/Setup/Base.pm +++ b/src/PVE/LXC/Setup/Base.pm @@ -267,6 +267,7 @@ sub setup_systemd_networkd { if (defined(my $ip = $d->{ip6})) { if ($ip eq 'dhcp') { $dhcp |=...

I don't have time to watch a video right now but we have a need to hook the start up of container to run socket CAN configuration as this isn't supported directly by Proxmox. The existing hook infrastructure let us see shutdown and start but if the node is rebooted on its own then our script...

No. At a minimum.

Could better IPv6 support please be prioritized. The change needed to make it work with Ubuntu containers is very minor. It's one setting in one file that PVE overrides to the wrong value. IPv6AcceptRA in /etc/systemd/network/eth0.network needs to be true not false. IPv6AcceptRA = true...

For reasons unexplained the Ubuntu containers come up with the below NIC configuration. Changing the PVE IPv6 network settings from Static/DHCP/SLAAC does not change this setting as is required. IPv6AcceptRA = false is virtually never the correct setting. It should default to listening to RA's...

I am not 100% certain as we as always in a hurry to get services back online when this happens but we have had several containers refuse to mount their LVM volume to start and this has happened multiple times. I suspect this happens if the backup storage runs out of space during the nightly...

One drive with LVM corruptions means restore-from-backup. Your hardware RAID controller has failed you. Consider LVM-RAID w/JBOD - far more reliable. Verify your drives support ZRAT/DRAT. If they do not then you should get new drives that do and failing that must disable TRIM and discard.

One of the servers is a few years old and it's conceivable the SSDs are wearing out as it s a build server and gets heavy use however we had no issues while it was running PVE7 but upgraded it as PVE7 went EOL and have been having issues with it since. Drives report they are at 70% lifetime. We...

To be clear we should not have to enable RA. RA is the required default behavior. As-is Proxmox does NOT support IPv6 because manual configuration override is required for all nodes for any proper IPv6 net.

We have non-FD CAN which is why I went out of my way to set the MTU to 16. it will default to 72 so you can just remove that part if you have FD. There is a hook system in Proxmox so on container start-up you can call a script. Put the script (or a symlink) in the /var/lib/vz/snippets/...

With 7.4-16 I have an Ubuntu container set to IPv6 DHCP and IPv6AcceptRA remains set to false. It was set to static at container creation then changed to DHCP. If I remove IPv6AcceptRA = false from the config file it comes back next reboot. The IPv6 settings almost should be Static, RA...

I couldn't get any information off of the host at the time because it had no network connection. I got a USB NIC and rebooted back into 6.2.16 / 8.0.3 and neither NIC worked. After a grub-install and update and another reboot both NICs started working. Suggest something was munged in my initrd...

It is no longer working on one of our older machines, a Z97 chipset, with a Qualcomm Atheros E220x NIC. This uses the alx driver LKW w/ Kernel 5.15.108-1-pve 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) Subsystem: Micro-Star...

I know this is a bit of a long-shot but maybe there are some others with similar use-cases. Right now Proxmox has integrated support for virtual-eth networking to containers and it works well. I really want to be able to add interfaces to a container for network devices other than Ethernet...

Wildcard certs and a way to share them with the containers during start-up would be a really nice feature to have. Provide a mount for it then have an optional way to trigger unmounting the cert once the service launches. This would help fix broken daemons like Mosquitto and Caddy that do not...