Search results

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.

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

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 – […]...

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

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.

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...

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?

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...