Recent content by itkfm

  1. I

    Slow backups sabotaging VMs

    To clarify: The issue is not that a slow backup stalles a VM. It’s rather that sometimes backups take forever for seemingly no reason. Involved storage: Local ZFS mirrors.
  2. I

    Slow backups sabotaging VMs

    Hi, We have seen multiple cases of oddly slow backups that end up sabotaging the VMs (stalling them to death). It happens across various constellations, locations and PBS versions. It’s not exactly deterministic, but there’s one server where it happened twice successively. I’ve not been able...
  3. I

    Tag colour and order not retaining override colour or order

    Screenshot is taken from v8.4.14 by the way.
  4. I

    Tag colour and order not retaining override colour or order

    Another oddity is that the search overview seems to get it right even at times where the datacenter tree does not.
  5. I

    "Locked backup group" error when syncing with an off-site PBS

    Issue opened: https://bugzilla.proxmox.com/show_bug.cgi?id=6566
  6. I

    "Locked backup group" error when syncing with an off-site PBS

    Seeing something similar here almost every week (for a weekly sync job). As there are no other tasks running at the same time (checked task history for multiple occurrences of this issue), it looks as if it the pushing PBS instance locks out itself from the receiving datastore by not releasing...
  7. I

    Hetzner Setup - dealing with MAC addresses

    Make sure your NAT works and the VMs are not connected to a bridge to the outside world. If you got the abuse message for the virtual machine’s MAC address, it was bridged to Hetzner’s infrastructure.
  8. I

    SDN No DHCP address when Datacenter firewall is enabled.

    Luckily, this is documented here: https://pve.proxmox.com/wiki/Setup_Simple_Zone_With_SNAT_and_DHCP#Firewall_Setup
  9. I

    Proxmox VE 8.2 released!

    Because a system might have just been upgraded to PVE 8. (As in 7.4 → 8.2) That’s an intended use-case. The script can detect post-upgrade issues (like a missing systemd-boot package on applicable systems). Like the Upgrade instructions say, “Continuously use the pve7to8 checklist script – […]...
  10. I

    Proxmox VE 8.2 released!

    Checking running kernel version.. WARN: unexpected running and installed kernel '6.8.4-3-pve'. Looks like pve7to8 could use an update.
  11. I

    Bug or incorrect docs: Overriding network device names

    While the docs say, PVE will only recognize those starting with en. Interfaces starting with eth, e.g. ethitkfm0, however will be treated as Unknown instead of a Network Device.
  12. I

    [SOLVED] Networking Issues

    No worries. You can also download the package manually from https://packages.ubuntu.com/noble/traceroute – and use an (optionally virtual) pen drive or disk (you can also mount the disk of a shutdown VM at the host) to get the file into your VM – or, if you have busybox installed, go with...
  13. I

    [SOLVED] Networking Issues

    Can you reach other hosts within the 192.168.178.0/24 subnet from your VM? What happens when you traceroute an IP address outside of your networks?
  14. I

    ifupdown2 defunct after updating to 8.2

    Long story short, with the new kernel of PVE 8.2 this machine here… hangs at the systemd-udev thing during boot for a while. boots with all network interfaces being down. takes forever to shutdown because of Failed to deinitialize RCFW followed by a stream of AMD-Vi IO_PAGE_FAULTs. Please...
Top Bottom
Back