Proxmox VE 8.2 released!
- Thread starter martin
- Start date
Hello,
Try (on my side works well):
edit:
/etc/default/grubset:
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).
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?
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,
EDIT: should be fixed now: https://forum.proxmox.com/threads/u...-remove-proxmox-ve-package.149101/post-675259
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:
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.
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.
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.