Proxmox VE 8.2 released!

There is an issue with the upgrade. Post upgrade network interfaces names have change

pre upgrade
ens4f0

Post upgrade
ens4f0np0

This has caused all user created bonds to go down

Needs to modify the network config file to bring up the nodes
 
There is an issue with the upgrade. Post upgrade network interfaces names have change

pre upgrade
ens4f0

Post upgrade
ens4f0np0

This has caused all user created bonds to go down

Needs to modify the network config file to bring up the nodes
This was mentioned in the release notes, but there's a lot of stuff in there.
See these instructions in the docs to pin the interface names: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#network_override_device_names
 
  • Like
Reactions: justinclift
Yesterday I did :
apt update
apt dist-upgrade

so it upgraded to proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve)

Now if I want to install a package I get this warning :

Code:
The following package was automatically installed and is no longer required:
  proxmox-firewall
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  proxmox-ve pve-container pve-ha-manager pve-manager qemu-server

Luckily there is a hook that prevents this from happening :

Code:
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook)     touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook)     - your APT repository settings
W: (pve-apt-hook)     - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook

Anyone else having this issue ?
 
Yesterday I did :
apt update
apt dist-upgrade

so it upgraded to proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve)

Now if I want to install a package I get this warning :
could you please post the complete output of:
* apt update
* apt full-upgrade
* apt install <package you want to install>
(do not remove proxmox-ve )
 
could you please post the complete output of:
* apt update
* apt full-upgrade
* apt install <package you want to install>
(do not remove proxmox-ve )
Do you mean the output of these after the upgrade ? or when doing the upgrade ?
I dont have the output anymore of when the upgrade happened.

Here is the full output of the last command :


Bash:
root@pve:~# apt-get install watchdog
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  proxmox-firewall
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  proxmox-ve pve-container pve-ha-manager pve-manager qemu-server
The following NEW packages will be installed:
  watchdog
0 upgraded, 1 newly installed, 5 to remove and 0 not upgraded.
Need to get 0 B/69.7 kB of archives.
After this operation, 4,332 kB disk space will be freed.
Do you want to continue? [Y/n]
 
Last edited:
I found the output of one of the upgrades :


Bash:
root@pve:~# apt update
apt full-upgrade
Hit:1 http://security.debian.org bookworm-security InRelease
Hit:2 http://download.proxmox.com/debian/pve bookworm InRelease
Hit:3 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Hit:4 http://ftp.be.debian.org/debian bookworm InRelease
Hit:5 http://ftp.be.debian.org/debian bookworm-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
16 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  proxmox-kernel-6.8.4-3-pve-signed
The following packages will be upgraded:
  less libc-bin libc-l10n libc6 libproxmox-acme-perl libproxmox-acme-plugins locales proxmox-backup-client proxmox-backup-file-restore proxmox-firewall proxmox-kernel-6.8 proxmox-widget-toolkit pve-container pve-docs
  pve-firewall pve-qemu-kvm
16 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 162 MB of archives.
After this operation, 578 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 libproxmox-acme-plugins all 1.5.1 [130 kB]
Get:2 http://security.debian.org bookworm-security/main amd64 libc6 amd64 2.36-9+deb12u7 [2,758 kB]
Get:3 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 libproxmox-acme-perl all 1.5.1 [11.1 kB]
Get:4 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-backup-client amd64 3.2.2-1 [2,926 kB]
Get:5 http://security.debian.org bookworm-security/main amd64 libc-bin amd64 2.36-9+deb12u7 [607 kB]
Get:6 http://security.debian.org bookworm-security/main amd64 less amd64 590-2.1~deb12u2 [132 kB]
Get:7 http://security.debian.org bookworm-security/main amd64 libc-l10n all 2.36-9+deb12u7 [675 kB]
Get:8 http://security.debian.org bookworm-security/main amd64 locales all 2.36-9+deb12u7 [3,902 kB]
Get:9 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-backup-file-restore amd64 3.2.2-1 [2,946 kB]
Get:10 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-firewall amd64 5.0.7 [73.0 kB]
Get:11 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-firewall amd64 0.4.1 [712 kB]
Get:12 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8.4-3-pve-signed amd64 6.8.4-3 [103 MB]
Get:13 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-kernel-6.8 all 6.8.4-3 [9,992 B]
Get:14 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 proxmox-widget-toolkit all 4.2.3 [214 kB]
Get:15 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-container all 5.1.10 [139 kB]
Get:16 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-docs all 8.2.2 [15.6 MB]
Get:17 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 pve-qemu-kvm amd64 8.1.5-6 [28.3 MB]
Fetched 162 MB in 3s (53.1 MB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 48255 files and directories currently installed.)
Preparing to unpack .../libc6_2.36-9+deb12u7_amd64.deb ...
Unpacking libc6:amd64 (2.36-9+deb12u7) over (2.36-9+deb12u6) ...
Setting up libc6:amd64 (2.36-9+deb12u7) ...
(Reading database ... 48255 files and directories currently installed.)
Preparing to unpack .../libc-bin_2.36-9+deb12u7_amd64.deb ...
Unpacking libc-bin (2.36-9+deb12u7) over (2.36-9+deb12u6) ...
Setting up libc-bin (2.36-9+deb12u7) ...
(Reading database ... 48255 files and directories currently installed.)
Preparing to unpack .../00-less_590-2.1~deb12u2_amd64.deb ...
Unpacking less (590-2.1~deb12u2) over (590-2) ...
Preparing to unpack .../01-libc-l10n_2.36-9+deb12u7_all.deb ...
Unpacking libc-l10n (2.36-9+deb12u7) over (2.36-9+deb12u6) ...
Preparing to unpack .../02-locales_2.36-9+deb12u7_all.deb ...
Unpacking locales (2.36-9+deb12u7) over (2.36-9+deb12u6) ...
Preparing to unpack .../03-libproxmox-acme-plugins_1.5.1_all.deb ...
Unpacking libproxmox-acme-plugins (1.5.1) over (1.5.0) ...
Preparing to unpack .../04-libproxmox-acme-perl_1.5.1_all.deb ...
Unpacking libproxmox-acme-perl (1.5.1) over (1.5.0) ...
Preparing to unpack .../05-proxmox-backup-client_3.2.2-1_amd64.deb ...
Unpacking proxmox-backup-client (3.2.2-1) over (3.2.0-1) ...
Preparing to unpack .../06-proxmox-backup-file-restore_3.2.2-1_amd64.deb ...
Unpacking proxmox-backup-file-restore (3.2.2-1) over (3.2.0-1) ...
Preparing to unpack .../07-pve-firewall_5.0.7_amd64.deb ...
Unpacking pve-firewall (5.0.7) over (5.0.5) ...
Preparing to unpack .../08-proxmox-firewall_0.4.1_amd64.deb ...
Unpacking proxmox-firewall (0.4.1) over (0.3.0) ...
Selecting previously unselected package proxmox-kernel-6.8.4-3-pve-signed.
Preparing to unpack .../09-proxmox-kernel-6.8.4-3-pve-signed_6.8.4-3_amd64.deb ...
Unpacking proxmox-kernel-6.8.4-3-pve-signed (6.8.4-3) ...
Preparing to unpack .../10-proxmox-kernel-6.8_6.8.4-3_all.deb ...
Unpacking proxmox-kernel-6.8 (6.8.4-3) over (6.8.4-2) ...
Preparing to unpack .../11-proxmox-widget-toolkit_4.2.3_all.deb ...
Unpacking proxmox-widget-toolkit (4.2.3) over (4.2.1) ...
Preparing to unpack .../12-pve-container_5.1.10_all.deb ...
Unpacking pve-container (5.1.10) over (5.0.10) ...
Preparing to unpack .../13-pve-docs_8.2.2_all.deb ...
Unpacking pve-docs (8.2.2) over (8.2.1) ...
Preparing to unpack .../14-pve-qemu-kvm_8.1.5-6_amd64.deb ...
Unpacking pve-qemu-kvm (8.1.5-6) over (8.1.5-5) ...
Setting up proxmox-backup-file-restore (3.2.2-1) ...
Updating file-restore initramfs...
12701 blocks
Setting up proxmox-kernel-6.8.4-3-pve-signed (6.8.4-3) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.4-3-pve /boot/vmlinuz-6.8.4-3-pve
update-initramfs: Generating /boot/initrd.img-6.8.4-3-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.4-3-pve /boot/vmlinuz-6.8.4-3-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.4-3-pve /boot/vmlinuz-6.8.4-3-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-systemd-boot 6.8.4-3-pve /boot/vmlinuz-6.8.4-3-pve
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.4-3-pve /boot/vmlinuz-6.8.4-3-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.4-3-pve
Found initrd image: /boot/initrd.img-6.8.4-3-pve
Found linux image: /boot/vmlinuz-6.8.4-2-pve
Found initrd image: /boot/initrd.img-6.8.4-2-pve
Found memtest86+x64 image: /boot/memtest86+x64.bin
done
Setting up proxmox-widget-toolkit (4.2.3) ...
Setting up libc-l10n (2.36-9+deb12u7) ...
Setting up pve-qemu-kvm (8.1.5-6) ...
Setting up less (590-2.1~deb12u2) ...
Setting up libproxmox-acme-perl (1.5.1) ...
Setting up locales (2.36-9+deb12u7) ...
Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.
Setting up pve-docs (8.2.2) ...
Setting up proxmox-backup-client (3.2.2-1) ...
Setting up libproxmox-acme-plugins (1.5.1) ...
Setting up pve-firewall (5.0.7) ...
Setting up proxmox-kernel-6.8 (6.8.4-3) ...
Setting up pve-container (5.1.10) ...
Setting up proxmox-firewall (0.4.1) ...
Processing triggers for pve-ha-manager (4.0.4) ...
Processing triggers for pve-manager (8.2.2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
 
i'm on a amd 7950x and was noticing daily random reboots, i've downgraded now to 6.5 kernel and pinned it. lets see how things go.

will report back in a week or so
 
I have problems with the new 6.8 kernel. Is it possible that the interface names change with an Intel X710 card? With 6.5 my interface was called enp99s0f0, with the 6.8 kernel the same interface is now called enp99s0f0np0. This tears up the entire network configuration...
This is why I am using legacy device ID's on Proxmox.
 
Code:
Checking running kernel version..
WARN: unexpected running and installed kernel '6.8.4-3-pve'.
Looks like pve7to8 could use an update.
 
Code:
Checking running kernel version..
WARN: unexpected running and installed kernel '6.8.4-3-pve'.
Looks like pve7to8 could use an update.
Why would you ever use the tool at a system that is already PVE 8?
 
Why would you ever use the tool at a system that is already PVE 8?
Because a system might have just been upgraded to PVE 8. (As in 7.4 → 8.2)

That’s an intended use-case. The script can detect post-upgrade issues (like a missing systemd-boot package on applicable systems).
Like the Upgrade instructions say, “Continuously use the pve7to8 checklist script – […] The program will provide hints and warnings about potential issues before, during and after the upgrade process.”
 
  • Like
Reactions: EvertM and jsterr
Moved to Proxmox 8.2 yesterday and had a VM crash just now.

Code:
[Thu May 16 13:29:43 2024] mce: Uncorrected hardware memory error in user-access at 10ac2b6b880
[Thu May 16 13:29:43 2024] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
[Thu May 16 13:29:43 2024] {1}[Hardware Error]: event severity: recoverable
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:  Error 0, type: recoverable
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:  fru_text: Card02, ChnE, DIMM1
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   section_type: memory error
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:    error_status: Storage error in DRAM memory (0x0000000000000400)
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   physical_address: 0x0000010ac2b6b880
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   node:1 card:4 module:1 rank:0 bank:7 device:0 row:8579 column:624
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   error_type: 4, single-symbol chipkill ECC
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   DIMM location: P1_Node2_Channel0_Dimm1 P2-DIMME2
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:  Error 1, type: recoverable
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:  fru_text: Card02, ChnE, DIMM1
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   section_type: memory error
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:    error_status: Storage error in DRAM memory (0x0000000000000400)
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   physical_address: 0x0000010ac2b6b880
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   node:1 card:4 module:1 rank:0 bank:7 device:0 row:8579 column:0
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   error_type: 3, multi-bit ECC
[Thu May 16 13:29:43 2024] {1}[Hardware Error]:   DIMM location: P1_Node2_Channel0_Dimm1 P2-DIMME2
[Thu May 16 13:29:43 2024] Memory failure: 0x10ac2b6b: Sending SIGBUS to kvm:5846 due to hardware memory corruption
[Thu May 16 13:29:43 2024] Memory failure: 0x10ac2b6b: recovery action for dirty LRU page: Recovered
[Thu May 16 13:29:43 2024] Memory failure: 0x10ac2b6b: already hardware poisoned
[Thu May 16 13:29:43 2024] Memory failure: 0x10ac2b6b: Sending SIGBUS to CPU 126/KVM:6534 due to hardware memory corruption
[Thu May 16 13:29:43 2024] Memory failure: 0x10ac2b6b: already hardware poisoned
[Thu May 16 13:29:43 2024] Memory failure: 0x10ac2b6b: already hardware poisoned
[Thu May 16 13:29:43 2024] EDAC skx MC6: HANDLING MCE MEMORY ERROR

Supermicro IPMI is reporting the memory as aok. Host has been solid on 6.5.x for months.

This is a quad socket host with 4th gen Intel's.

With all the talk about lockups etc in this thread, im starting to question if 6.8.x was a good move.

I feel like we are compromising bleeding edge for stability with updates as of late.
 
Last edited:
  • Like
Reactions: wommy

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!