Search results

Thanks, that worked!

I'm a freelance Postgres DBA and use Proxmox to host a plethora of containers and VMs for work (research mainly) for my clients. It's been an absolute godsend, so a huge THANKS for making Proxmox! I found the new OCI support interesting, so I searched the OCI registry for "postgres" and chose...

So cpu type "host" makes Windows 11 significantly slower (see https://forum.proxmox.com/threads/cpu-type-host-is-significantly-slower-than-x86-64-v2-aes.159107/ ), but switching away from it you get a yellow warning flag in Windows Security for memory integrity. Is there no way to get both...

Fantastic!!

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.