Proxmox VE 8.0 released!

Great work proxmox team.
I have a small doubt. In the prerequisites you say "Co-installed Proxmox Backup Server should wait until a public beta or final version will be released". Does that mean that if a have a PBS as a VM on my proxmox host i must not update yet and wait for a PBS beta at least?
 
Great work proxmox team.
I have a small doubt. In the prerequisites you say "Co-installed Proxmox Backup Server should wait until a public beta or final version will be released". Does that mean that if a have a PBS as a VM on my proxmox host i must not update yet and wait for a PBS beta at least?
Coinstalled means that you install it directly without a extra vm on the hypervisor host. Means https://ip-pve:8006 is your PVE and https://ip-pve:8007 is your pbs, same host.
 
Anyone seen this warning ?

WARN: proxmox-boot-tool is used for bootloader configuration in uefi modebut the separate systemd-boot package, existing in Debian Bookworm is not installedinitializing new ESPs will not work until the package is installed
 
  • Like
Reactions: DAVe3283
Anyone seen this warning ?

WARN: proxmox-boot-tool is used for bootloader configuration in uefi modebut the separate systemd-boot package, existing in Debian Bookworm is not installedinitializing new ESPs will not work until the package is installed
This warning says that your system uses proxmox-boot-tool for booting (which is the case for systems with '/' on ZFS installed by the PVE installer).
In the UEFI case the system uses systemd-boot for booting - see [0]. Until bullseye systemd-boot was part of the systemd main package, with bookworm it became a package of its own (systemd-boot). Since the new package installs hooks and automatically installs systemd-boot on a mounted ESP (which is the case for systems installed with LVM) we did not pull it in unconditionally upon upgrade.
for proxmox-boot-tool the systemd-boot package itself is only needed if you initialize new ESPs (e.g. when changing a faulted disk in your ZFS RAID [1]) - so your system remains bootable even without systemd-boot installed - You can simply install systemd-boot and the warning will vanish

I hope this explains it!

[0] https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot
[1] https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_zfs_administration
 
Seeing the same thing on real hardware here.

Hi, I think I've found another issue with the graphical installer. Seems like it doesn't set / save the selected hard disks correctly when chosing them for a RAID. I've attached a screencast to demonstrate.

Am I doing something wrong? Totally an option as well

https://youtu.be/Gn7UDup2Gjs

best regards
can confirm this issue, we are working on a fix and re-rolled iso!
 
This actually confuses me now:

Either
Code:
apt-get update
apt-get dist-upgrade
or
Code:
apt update
apt full-upgrade

Does anyone know the answer?
dist-upgrade && full-upgrade is exactly the same thing.

Code:
https://salsa.debian.org/apt-team/apt/-/blob/main/cmdline/apt.cc#L77

 {"full-upgrade", &DoDistUpgrade, _("upgrade the system by removing/installing/upgrading packages")},

https://salsa.debian.org/apt-team/apt/-/blob/main/cmdline/apt.cc#L85
      // for compat with muscle memory
      {"dist-upgrade", &DoDistUpgrade, nullptr},
 
Last edited:
  • Like
Reactions: jsterr
Hi, I think I've found another issue with the graphical installer. Seems like it doesn't set / save the selected hard disks correctly when chosing them for a RAID. I've attached a screencast to demonstrate.

Am I doing something wrong? Totally an option as well

https://youtu.be/Gn7UDup2Gjs

best regards
can confirm this issue, we are working on a fix and re-rolled iso!

not new one, but glad to hear that it's getting adressed now: https://bugzilla.proxmox.com/show_bug.cgi?id=4473
 
Last edited:
Hi, I think I've found another issue with the graphical installer. Seems like it doesn't set / save the selected hard disks correctly when chosing them for a RAID. I've attached a screencast to demonstrate.

Am I doing something wrong? Totally an option as well

https://youtu.be/Gn7UDup2Gjs

best regards
Seeing the same thing on real hardware here.
FYI, the refreshed ISO proxmox-ve_8.0-2.iso is out now on the CDN and www.proxmox.com, it only has an updated installer as change with a few targeted fixes for existing bugs that only stuck out now, i.e., some HD size/max LVM overrides, smaller disk sizes, and also a fix for the raid disk selection, which is now preserved including the order.

The launch of the TUI based installer mode was slightly bumpier than we'd have liked, but thanks to all of your quick feedback, the discussion for targeted fixes of developers and confirming those fixes, we could resolve this quickly enough and will ensure raid disks selection including order, especially of mixed sizes, is always taken a closer look at in future installer QA.
 
not new one, but glad to hear that it's getting adressed now: https://bugzilla.proxmox.com/show_bug.cgi?id=4473
This particular issue has not been addressed by the 8.0 ISO - just not not cause more confusion.

We quickly looked it through - and one option we came up with is that we might make installation with mixed-size disks as mirror-pairs (or in a raid-zX vdev) possible by letting the user explicitly select a hdsize in the installer (which is less or equal to the smallest disk)
However this will come earliest with a future 8.1 (not promises of course)
 
Hello. I get error messages regarding squashfs command (the installer says that there is an error in line 870 of Install.pm file). The error pops up and installation breaks.
I get similar error (different line) both on 8.0.1 and 8.0.2. I didn't have such error when installing 7.3 version of proxmox.
My hardware - HP 600 g3 - 2 nvme disks (one is the target for installation), 2 hdd 2.5 inch; 24 GB RAM, installation medium - USB disk (sha256 is correct)
 
Last edited:
FYI, the refreshed ISO proxmox-ve_8.0-2.iso is out now on the CDN and www.proxmox.com, it only has an updated installer as change with a few targeted fixes for existing bugs that only stuck out now, i.e., some HD size/max LVM overrides, smaller disk sizes, and also a fix for the raid disk selection, which is now preserved including the order.

The launch of the TUI based installer mode was slightly bumpier than we'd have liked, but thanks to all of your quick feedback, the discussion for targeted fixes of developers and confirming those fixes, we could resolve this quickly enough and will ensure raid disks selection including order, especially of mixed sizes, is always taken a closer look at in future installer QA.
Thank you very much
 
Hello. I get error messages regarding squashfs command (the installer says that there is an error in line 870 of Install.pm file). The error pops up and installation breaks.
I get similar error (different line) both on 8.0.1 and 8.0.2. I didn't have such error when installing 7.3 version of proxmox.
My hardware - HP 600 g3 - 2 nvme disks (one is the target for installation), 2 hdd 2.5 inch; 24 GB RAM, installation medium - USB disk (sha256 is correct)
Since the ISO works for most other people here (and for us internally) I don't think that the issue is indeed an error in the perl-code of the installer.

I'd suggest to try a different USB drive, and maybe also different software for transferring the ISO to the USB (plain linux dd works definitely)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!