host-managed=0 should be the closest equivalent to PVE8 behavior, though PVE9 does include logic to auto-detect if the host or guest should configure the network and it is usually not necessary to specify it.
Specifically, it checks the existence...
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
That feels like a documentation error, as in every other Ceph upgrade guide "ceph osd require-osd-release <new_release>" is used just after every OSD has been restarted.
Today we're introducing a dedicated repository for debug symbol packages, reachable at https://dbgsym.proxmox.com/.
Debug symbol packages (named <package>-dbgsym) contain the detached debug information for their matching binary package. They are...
That's what I usually do: using 2 vlans over the same bond add the benefit that if you ever need to separate the cluster network to a different bond, no Ceph configuration changes will have to be made (i.e. add the cluster network and restart...
During PVE install, the ISO installer will try to get an IP from DHCP. If that succeeds, it will configure that IP as static for vmbr0. As you are not very experienced, I suggest that you create a DHCP reservation assigned to the MAC of your PVE...
Wouldn't it be more precise to say that PVE on DHCP isn't supported without other tweaks even on single node setups?
Some services require to resolve the host name to an IP that is currently assigned to the host to work properly.