I'm no expert, but i would guess so.
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.html
Module 'restful' has failed dependency: PyO3 modules may only be initialized once per interpreter processModule 'restful' has failed dependency: PyO3 modules may only be initialized once per interpreter process
currently, permissions management for local vmbrX . (mandatory now if you are not administrator)
do you have enabled ceph-dashboard ? (because it seem to be incompatbile with a new python lib pyo3 0.17 version on debian12)
Ah, yes, I do.
proxmox-ve_8.0-2.iso image mounted as a virtual CD to a Dell R740xd via iDrac9. Everything seemed fine as I specified a pair of disks (last pair out of 26 SATA SSDs on the HBA) to setup as ZFS RAID1 and configured the network. The installer went through to the end without error and rebooted to EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path on a black screen. I tried a few times with/without auto-reboot after install and with/without disconnecting the virtual media before rebooting. No change. I also tried on a second identical host with same result. I then tried just installing to the first disk without ZFS and that booted (albeit now with a blue grub screen appearing instead of a black systemd-boot(?) one.)
If you want to use that, I'd recommend testing it first in an unimportant setup (e.g., a virtual Proxmox VE instance mirroring roughly what your real setup looks like). Debian's recommendation for some cases, as they write, is a relatively safe thing to do in general, but it's definitively not a must nor a recommendation for PVE hosts, among other things as we did not really test that approach extensively - and note that for the "actual" update you must NOT use the apt upgrade command, but
full-upgrade (or its alias dist-upgrade)!A one step upgrade is not a hard requirement, but what we recommend, especially if unsure, and what we tested most.
Yes, we will continue to ship updates for the whole release cycle of Proxmox VE 8, just like we did for Proxmox VE 7, continuosly fixing bugs and also providing more features.
Maybe, but then you'd practically wait until Proxmox VE 8 is EOL in ~three years or so, as only then we will stop releasing updates for this release
.
systemd-boot package.systemd-boot package just ensures that you get future updates to that binary and also that you can initialize new drives as boot devices, for example if one of a rpool root mirror needs to be replaced in the future.2023-06-24T17:23:07.249280+02:00 proxmox kernel: [ 3309.419261] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-06-24T17:23:07.249285+02:00 proxmox kernel: [ 3309.420982] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-06-24T17:23:07.253285+02:00 proxmox kernel: [ 3309.422741] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
2023-06-24T17:23:07.281274+02:00 proxmox kernel: [ 3309.452104] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-06-24T17:23:07.313268+02:00 proxmox kernel: [ 3309.482136] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
2023-06-24T17:23:07.341302+02:00 proxmox kernel: [ 3309.512139] r8169 0000:02:00.0 enp2s0: rtl_eriar_cond == 1 (loop: 100, delay: 100).
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
iface lo inet6 loopback
auto enp7s0
iface enp7s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 1.2.3.4/26
gateway 1.2.3.193
bridge-ports enp7s0
bridge-stp off
bridge-fd 0
hwaddress rr:ii:uu:bb:aa:xx
up ip route add 1.2.3.1/26 via 1.2.3.193 dev vmbr0
up ip route add 1.2.2.1/32 dev vmbr0
#VMs
iface vmbr0 inet6 static
address 2a01:yyy:xxx:fa00::2/64
gateway fe80::1
up ip -6 route add 2a01:yyy:xxx:fa00::/56 via 2a01:yyy:xxx:fa00::3
