Proxmox VE 8.2 released!

antreos said:
As written here:
  • #13

    6.8.4-3-pve didn't fix the issue
Click to expand...
Hello,

Try (on my side works well):

edit: /etc/default/grub
set: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=off"
MAIN KEY: intel_iommu=off
On my side server is now stable. BIOS on my mainboard (gigabytes) have probably some issues (but not upgrades available).
 
  • Like
Reactions: antreos
razit said:
Hello,

Try (on my side works well):

edit: /etc/default/grub
set: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=off"
MAIN KEY: intel_iommu=off
On my side server is now stable. BIOS on my mainboard (gigabytes) have probably some issues (but not upgrades available).
Click to expand...
The first tests succeeded, thanks a lot! Will monitor it closely. Did not solve it.
 
Last edited:
Code: 
# apt-get clean; apt-get update; apt -o Debug::pkgProblemResolver=yes install --reinstall pve-manager
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Hit:5 http://download.proxmox.com/debian/pve bookworm InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) pve-container:amd64 < 5.1.10 -> 5.1.11 @ii puU Ib >
Broken pve-container:amd64 Depends on libpve-guest-common-perl:amd64 < 5.1.2 | 5.1.3 @ii uH > (>= 5.1.3)
  Considering libpve-guest-common-perl:amd64 8 as a solution to pve-container:amd64 6
  Re-Instated libpve-guest-common-perl:amd64
Broken pve-container:amd64 Depends on proxmox-backup-client:amd64 < 3.2.3-1 @ii K > (>= 3.2.5-1)
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
 pve-container : Depends: proxmox-backup-client (>= 3.2.5-1) but 3.2.3-1 is to be installed
E: Unable to correct problems, you have held broken packages.

but I don't see proxmox-backup-client >= 3.2.5-1 anywhere. Hm?
 
are said:
Code: 
# apt-get clean; apt-get update; apt -o Debug::pkgProblemResolver=yes install --reinstall pve-manager
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Hit:5 http://download.proxmox.com/debian/pve bookworm InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) pve-container:amd64 < 5.1.10 -> 5.1.11 @ii puU Ib >
Broken pve-container:amd64 Depends on libpve-guest-common-perl:amd64 < 5.1.2 | 5.1.3 @ii uH > (>= 5.1.3)
  Considering libpve-guest-common-perl:amd64 8 as a solution to pve-container:amd64 6
  Re-Instated libpve-guest-common-perl:amd64
Broken pve-container:amd64 Depends on proxmox-backup-client:amd64 < 3.2.3-1 @ii K > (>= 3.2.5-1)
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
 pve-container : Depends: proxmox-backup-client (>= 3.2.5-1) but 3.2.3-1 is to be installed
E: Unable to correct problems, you have held broken packages.

but I don't see proxmox-backup-client >= 3.2.5-1 anywhere. Hm?
Click to expand...

Same Problem here, when installing on debian 12 using "apt install proxmox-ve".
3.2.5-1 seems to not exist here http://download.proxmox.com/debian/pve/dists/bookworm/pve-no-subscription/binary-amd64/. But 3.2.5-1 changelog exists
 
Hi,
are said:
Code: 
# apt-get clean; apt-get update; apt -o Debug::pkgProblemResolver=yes install --reinstall pve-manager
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://download.proxmox.com/debian/ceph-reef bookworm InRelease
Hit:5 http://download.proxmox.com/debian/pve bookworm InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) pve-container:amd64 < 5.1.10 -> 5.1.11 @ii puU Ib >
Broken pve-container:amd64 Depends on libpve-guest-common-perl:amd64 < 5.1.2 | 5.1.3 @ii uH > (>= 5.1.3)
  Considering libpve-guest-common-perl:amd64 8 as a solution to pve-container:amd64 6
  Re-Instated libpve-guest-common-perl:amd64
Broken pve-container:amd64 Depends on proxmox-backup-client:amd64 < 3.2.3-1 @ii K > (>= 3.2.5-1)
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:


The following packages have unmet dependencies:
 pve-container : Depends: proxmox-backup-client (>= 3.2.5-1) but 3.2.3-1 is to be installed
E: Unable to correct problems, you have held broken packages.

but I don't see proxmox-backup-client >= 3.2.5-1 anywhere. Hm?
Click to expand...
ChuckNorris99 said:
Same Problem here, when installing on debian 12 using "apt install proxmox-ve".
3.2.5-1 seems to not exist here http://download.proxmox.com/debian/pve/dists/bookworm/pve-no-subscription/binary-amd64/. But 3.2.5-1 changelog exists
Click to expand...
a fix is being worked on, see: https://forum.proxmox.com/threads/u...-remove-proxmox-ve-package.149101/post-675210

EDIT: should be fixed now: https://forum.proxmox.com/threads/u...-remove-proxmox-ve-package.149101/post-675259
 
Last edited:
  • Like
Reactions: ChuckNorris99
razit said:
Hello,

Try (on my side works well):

edit: /etc/default/grub
set: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=off"
MAIN KEY: intel_iommu=off
On my side server is now stable. BIOS on my mainboard (gigabytes) have probably some issues (but not upgrades available).
Click to expand...
unfortunately, I had a crash again today, rendering the PVE completely offline needing a hard reset. maybe proxmox staff has ideas?
 
When I upgraded my Proxmox server from kernel 6.5.13-5 to the opt-in 6.8.4-2 I experienced one of my VM's frequently freezing. This is a TrueNAS-SCALE VM running a ZFS-Pool. I therefor had pinned 6.5.13-5 as preffered kernal.

Upgrading to Proxmox 8.2 and the 6.8.4-3 kernel the VM was no longer freezing.

Today I have upgraded Proxmox, the kernel was upgraded to 6.8.8-1. Within a few hours after the upgrade the VM is freezing again. It appears that something that got fixed in 6.8.4-3 is now again broken in 6.8.8-1.

Edit 2024-06-26: I have not pinned another kernel since the freeze as mentioned above. Have only rebooted the frozen VM, and it has been running stable ever since. It appears it only freezes after a reboot of Proxmox or something. I will investigate this further. But so far running 6.8.8-1 for now has been ok since I have rebooted the frozen VM.
 
Last edited:
Proxmox is so unstable right now that I have shut down my home server (with everything on it) and just have to wait until a stable kernel and version is released. I have used Proxmox for about 8 years and this is the most unstable it has been for me. I don't have the time right now to reinstall a previous iso version along with all my vm's. Just have to wait this one out.
 
My server started to freeze randomly too after the update.
Never ever was freezing before.
Seems related.
 
Just wondering, which kernel version is used in latest PVE Enterprise repo, if that's not secret information?

We upgraded some of our clusters to latest PVE 8.2, however the nodes still run w/o reboot using 6.5.11-7-pve kernel.
 
bomzh said:
Just wondering, which kernel version is used in latest PVE Enterprise repo
Click to expand...
For me it is:
Linux xxx 6.8.4-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.4-3 (2024-05-02T11:55Z) x86_64 GNU/Linux

Edit: dependencies:
Code: 
~# apt depends proxmox-default-kernel proxmox-kernel-6.8
proxmox-default-kernel
  Depends: proxmox-kernel-6.8
proxmox-kernel-6.8
  Depends: pve-firmware
 |Depends: proxmox-kernel-6.8.4-3-pve-signed
  Depends: proxmox-kernel-6.8.4-3-pve
    proxmox-kernel-6.8.4-3-pve-signed
  Replaces: <pve-kernel-6.8>
    proxmox-kernel-6.8
 
Last edited:
  • Like
Reactions: bomzh
dsi said:
I'm using Proxmox for years. The upgrade went without any issues (as usual - thanks Proxmox team!) But the latest 6.8 kernel upgrade results in unpredictable crashes (several days) on my HPE Microserver Gen8 (back to 6.5 now and stable) - nothing suspicious in the logs, just bang and reboot. The Supermicro X11SBA runs without any problems.
Click to expand...
Update: the unpredictables crashes appeared on the Gen8 with kernel 6.8.4-3. Newer kernel 6.8.8-1 on the same machine is running stable here for >10 days now.
 
  • Like
Reactions: razit
dsi said:
Update: the unpredictables crashes appeared on the Gen8 with kernel 6.8.4-3. Newer kernel 6.8.8-1 on the same machine is running stable here for >10 days now.
Click to expand...
On my side too, but for now uptime is now ~7 days
 
mgabriel said:
Congratulations :)

Is the esxi importer already available in the enterprise repo?
Click to expand...
When we importing Linux VM from ESXi To Proxmox .Linux VMs like Centos7 going to Rescue mode. but Window 11 and WIndows 2022 are working fine
 
I have an impression that ISO of v.8.2-1 is not consistent.

I get errors during installation:
Code: 
zstd uncompress failed with error code 20
command 'unsquashfs -f -dest /target -i /cdrom/pve-base.squashfs' failed with exit code 1
proxmox FATAL ERROR: writer: failed to read/uncompress file /target/usr/lib/python3.11/re/__pycache__/_parser.cpython-311.pyc

I tried two different media (microSD), two different destination drives (SSDs), tried to flash ISO with BalenaEtcher and Rufus - all the time the same error in all possible combinations.
Only when I tried version 7.4-1 - it worked without any problems.

Regarding flashing ISO to media - I tried recommended BalenaEtcher and Rufus. Latest Rufus automatically uses DD mode, so that was also not a problem.

Update: same problem with v.8.1-2
 
Last edited:
gfngfn256 said:
Were you able to update to latest version after that? Your HW may have a problem with the latest kernels.
Click to expand...
I'm quite new to Proxmox, thanks for the idea. After your question I did upgrade and it finished successfully. Now I have v.8.2.4.
HW is a bit old. It's HP EliteDesk 800 G2. Next week I'll have an opportunity to try on more modern HW. Will see how it'll run with ISO image.
Thanks again for the idea!
 
  • Like
Reactions: gfngfn256
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back