Search results

Just warning and booting anyway instead of erroring out would be even better! What's the worst that could happen?

I wonder if there's an easy way for you to provide a mechanism for us users to be able to "force" boot an unsupported distro. Many command line tools have "--force" options. In this case we have to resort to editing a packaged file to change the test. I wonder if you could have a "conf.d"...

Depends entirely on what other changes you've made since installation. I usually upgrade in place.

Just wondering when the Debian 13 Trixie container template will be available?

Thanks. There were no updates available earlier, but there are now, and after installation pve8to9 is now installed.

pve8to9 not found. I have to presume it's still coming?

I use Proxmox extensively in my homelab where I have virtual machines for many of my clients (I'm a freelance Postgres DBA and need to keep development / scratch machines separate). It would be nice to be able to grow and shrink resource usage even more and it got me wondering about hotplug...

Thanks. Ran into the exact some situation here.

And now after several reboots it's working fine again, but nothing has changed in the config...

Did you ever diagnose this problem? I'm experiencing the exact same symptoms. Running PVE 8.3, recently upgraded from PVE 6.4. I have just downgraded from the 6.11 to the 6.8 kernel to see if it makes any difference. My network config is 4 NICs: 2 and 2 in LACP bonds; those two active-backup...

Yes, thanks from me too @bochen415 . Hopefully upstream can be fixed to not reboot when fast boot is enabled in Windows.

That fixed it. The first two shutdowns I tried worked immediately.

Tell me and we'll both know. In some ways it's good to know I'm not the only one.

No HA. Just a plain vanilla VM.

Huh? /etc/network/interfaces has as last line source /etc/network/interfaces.d/* so there is no need to duplicate definitions that are included in any file in that directory. The SDN config is activated by and integrated with systemd in this way. And without that source line, SDN won't work.

I think you missed the bit where it's working on my Ethernet-only machines without enabling forwarding using /proc/sys/net/ipv4/ip_forward -- which I presume is what the ip-forward on in the generated /etc/network/interfaces.d/sdn is supposed to achieve.

The only thing that is needed is to edit /etc/sysctl.conf and uncomment net.ipv4.ip_forward=1. For some reason this is needed on WiFi machines but not on machines with Ethernet as their primary interface. Go figure.

Question: Why do you define vnet1 both in /etc/network/interfaces and through SDN (which ends up in /etc/network/interfaces.d/sdn?

I've been trying to setup a laptop with Proxmox for working on the road. I have no bridge configured, only a WiFi interface. The laptop is a member of my home development cluster, and everything seems to work perfectly. The WiFi interface on the laptop and the vmbr0 interfaces on the other...

Windows 11 24H2 guest on Proxmox 8.2.7 On shutdown it goes through the whole shutdown process but then the UEFI just boots it again... Under VirtualBox 7.1.4 on macOS 15.0.1 Windows 11 23H2 shuts down as expected. Where should I start looking?