Cannot update from 9.0.11 to 9.1.1

D

digipen79

New Member
Jan 30, 2025
18
2
3
I have been trying all morning to update from 9.0.11 to 9.1.1, but pve-manager and qemu-server both refuse to install no matter what I try. I will provide as much info as possible to help get this resolved.
 
Hi,
please share the output of apt update and the full output of the failed upgrade command as well as pveversion -v
 
Code: 
root@r630:~# apt update
Hit:1 http://download.proxmox.com/debian/ceph-squid trixie InRelease
Hit:2 http://download.proxmox.com/debian/pve trixie InRelease
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@r630:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  pve-manager qemu-server
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
root@r630:~# pveversion -v
proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve)
pve-manager: 9.0.11 (running version: 9.0.11/3bf5476b8a4699e2)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
proxmox-kernel-6.17: 6.17.2-1
proxmox-kernel-6.17.1-1-pve-signed: 6.17.1-1
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14: 6.14.11-4
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx11
intel-microcode: 3.20250512.1~deb11u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.4
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.0.15
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.3
libpve-rs-perl: 0.11.3
libpve-storage-perl: 9.0.18
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.20-1
proxmox-backup-file-restore: 4.0.20-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.2
pve-cluster: 9.0.7
pve-container: 6.0.18
pve-docs: 9.1.1
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.0.8
pve-i18n: 3.6.2
pve-qemu-kvm: 10.1.2-4
pve-xtermjs: 5.5.0-3
qemu-server: 9.0.24
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
 
Looks like I had them but they were set to Enabled:false for some reason! I removed that line and the update has worked though
 
  • Like
Reactions: danmac
Hello,
i have the same issue. Upgrade stucks at pve-manager. Debias repos are available and active.

Code: 
cat /etc/apt/sources.list.d/debian.sources
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie trixie-updates
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg



apt update
Hit:1 http://download.proxmox.com/debian/pve trixie InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Hit:4 http://deb.debian.org/debian trixie-updates InRelease
Reading package lists... 59%
All packages are up to date.
 
Hi,
snowflakes said:
i have the same issue. Upgrade stucks at pve-manager.
Click to expand...
what is the exact message you get?
snowflakes said:
apt update
Hit:1 http://download.proxmox.com/debian/pve trixie InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Hit:4 http://deb.debian.org/debian trixie-updates InRelease
Reading package lists... 59%
All packages are up to date.[/CODE]
Click to expand...
What does pveversion -v say?
 
fiona said:
Hi,

what is the exact message you get?

What does pveversion -v say?
Click to expand...
The message is: Setting up pve-manager (9.1.1) ...

Code: 
pveversion -v
proxmox-ve: not correctly installed (running kernel: 6.17.2-1-pve)
pve-manager: not correctly installed (running version: 9.1.1/42db4a6cf33dac83)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
proxmox-kernel-6.17: 6.17.2-1
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14: 6.14.11-4
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx11
intel-microcode: 3.20250812.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.4
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.0.15
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.3
libpve-rs-perl: 0.11.3
libpve-storage-perl: 9.0.18
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.20-1
proxmox-backup-file-restore: 4.0.20-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.2
pve-cluster: 9.0.7
pve-container: 6.0.18
pve-docs: 9.1.1
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.0.8
pve-i18n: 3.6.2
pve-qemu-kvm: 10.1.2-4
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.0
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1

The process list shows:
Code: 
  2799 pts/1    Ss+    0:00 /usr/bin/dpkg --status-fd 26 --configure --pending
  2800 pts/1    S+     0:00 /bin/sh /var/lib/dpkg/info/pve-manager.postinst configure 9.1.1
|/CODE]
 
Last edited:
Dear Onslow, thank your for the hint. I already did this (kill the processes, removed the locks). It does not work. The system is a Minisforum MS-01 with two NVME drives as ZFS mirror. I am afraid ia have to install from scratch. It is may not problem with proxmox in general, may my environment.
I installed proxmox in VirtualBOx for a test (9.0.1) and then upgrade, this upgrade works perfect.
 
Last edited:
Today i tried to simulate what happened on my ms-01. I haven older HP Elitdesk mini. I installen Proxmox 9.01. After that i tried update via Proxmox GUI. Worked flawless. Then i decided to do a backup of all VM and Container, afterwards i did the same procedure. Update via Proxmox GUI. Also worked flawless on my two reaminig nodes. Only the third one, no matter what i do, no chance to get it runnig. The difference in doing is, on the failed node, i did apt update and apt upgrade while logged in via ssh. On top comes that one of the NVME slots is dead. The NVME drives are not longer reachable. Even if i boot from SystemRescueCD. I also swapped the NVMEs, The slot is dead, the device is just 6 weeks old. Frustrating.
 
Same here, it was a pxx9 installation, no upgrade from older version before. I triggered the update from the gui which led to the above described problem.

A little bit digging came down to dependency errors ... but why (see my closing comment for a trace)?

cat /etc/apt/sources.list.d/debian.sources
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

----

apt update
Hit:1 http://deb.debian.org/debian trixie-updates InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease
Hit:3 http://download.proxmox.com/debian/pve trixie InRelease
2 packages can be upgraded. Run 'apt list --upgradable' to see them.

---

apt list --upgradable
pve-manager/stable 9.1.1 all [upgradable from: 9.0.11]
qemu-server/stable 9.1.0 amd64 [upgradable from: 9.0.23]

---

apt-mark showhold

(no output)

---

apt install --only-upgrade pve-manager qemu-server
Solving dependencies... Error!
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:

Unsatisfied dependencies:
qemu-server : Depends: python3-virt-firmware but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:
1. qemu-server:amd64=9.1.0 is selected as an upgrade
2. qemu-server:amd64=9.1.0 Depends python3-virt-firmware
but none of the choices are installable:
[no choices]

----

... and the pve-manager depends on qemu-server

afair python3-virt-firmware should be in debian main repository so it seems to be missing from the non subscription pve repository:

cat /etc/apt/sources.list.d/proxmox.sources
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
 
Last edited:
tom_tav said:
cat /etc/apt/sources.list.d/debian.sources
Types: deb
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Click to expand...
tom_tav said:
apt update
Hit:1 http://deb.debian.org/debian trixie-updates InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease
Hit:3 http://download.proxmox.com/debian/pve trixie InRelease
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
Click to expand...

tom_tav said:
afair python3-virt-firmware should be in debian main repository [...]
Click to expand...

So, the conclusion would be, to also have the trixie suite set up, no?:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_debian_base_repositories
 
No, otherwise you have the same packages in 2 repositories, one original and one proxxmox version. Smells like troubles....

Lets see if somebody from Proxxmox chimes in
 
tom_tav said:
No, otherwise you have the same packages in 2 repositories, one original and one proxxmox version. Smells like troubles....

Lets see if somebody from Proxxmox chimes in
Click to expand...

Not sure why you think python3-virt-firmware is, respectively should be, also in the PVE repositories.
It comes from the Debian trixie/main repository and I strongly assume that this is exactly how it is intended.

Generally, a PVE-host is supposed to have all of the Debian repositories as well as a appropriate PVE and Ceph repository respectively configured like mentioned here:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_package_repositories

But I am not here to convince anyone; good luck...
 
  • Like
Reactions: tom_tav
Neobin said:
Not sure why you think python3-virt-firmware is, respectively should be, also in the PVE repositories.
It comes from the Debian trixie/main repository and I strongly assume that this is exactly how it is intended.

Generally, a PVE-host is supposed to have all of the Debian repositories as well as a appropriate PVE and Ceph repository respectively configured like mentioned here:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_package_repositories

But I am not here to convince anyone; good luck...
Click to expand...
I agree with this ;) Proxmox VE is based upon Debian, and doesn't duplicate or mirror all packages in Debian.

tom_tav said:
No, otherwise you have the same packages in 2 repositories, one original and one proxxmox version. Smells like troubles....
Click to expand...
Having the same package in multiple repositories is not an issue per se. And if it's not actually the very same package, we make sure that it has a different version. For example, sometimes we need to rebuild a package with an additional fix:
Code: 
[I] root@pve9a1 ~# apt policy lvm2
lvm2:
  Installed: 2.03.31-2+pmx1
  Candidate: 2.03.31-2+pmx1
  Version table:
 *** 2.03.31-2+pmx1 500
        500 http://repo.proxmox.com/staging/pve trixie/pve-9 amd64 Packages
        500 http://download.proxmox.com/debian/pve trixie/pve-test amd64 Packages
        100 /var/lib/dpkg/status
     2.03.31-2 500
        500 http://deb.debian.org/debian trixie/main amd64 Packages
 
fiona said:
I agree with this ;) Proxmox VE is based upon Debian, and doesn't duplicate or mirror all packages in Debian.


Having the same package in multiple repositories is not an issue per se. And if it's not actually the very same package, we make sure that it has a different version. For example, sometimes we need to rebuild a package with an additional fix:
Code: 
[I] root@pve9a1 ~# apt policy lvm2
lvm2:
  Installed: 2.03.31-2+pmx1
  Candidate: 2.03.31-2+pmx1
  Version table:
 *** 2.03.31-2+pmx1 500
        500 http://repo.proxmox.com/staging/pve trixie/pve-9 amd64 Packages
        500 http://download.proxmox.com/debian/pve trixie/pve-test amd64 Packages
        100 /var/lib/dpkg/status
     2.03.31-2 500
        500 http://deb.debian.org/debian trixie/main amd64 Packages
Click to expand...

so what is the solution, just enable the main debian repro? I guess i mixed patched kernel with patched main system in my memory ;)
 
Last edited:
Oh yes, stupid me. I just checked for the debian-sources but missed that i had only trixie-updates and not trixie in it.

Thanks 4 your help!
 
You must log in or register to reply here.
Top Bottom