Proxmox VE 8.1 released!

marcus.cps said:
To be able to update the kernel to 6.5.11-4-pve, WITH R8168 kernel module working, you need to build the kernel module for the new version of the kernel. The module was previously build for the kernel version you were running.

To fix it you'll need to get the kernel headers for the new version:

Code: 
apt-get install linux-headers-6.5.11-4-pve

Second, you'll need to fix the kernel module source code, as Realtek did not really update the source code so it builds correctly for kernel 6.5. Luckily, fixing it is simple. Check my notes in the end for a technical explanation for the issue.

Edit the following file with your favourite editor:

Code: 
nano /usr/src/r8168-8.051.02/r8168_n.c

Then add the following line to the beginning of it:
Code: 
#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,4,10)
#include <net/gso.h>
#endif

My suggestion is, you should add it in between the 2 lines below:

Code: 
#include <linux/netdevice.h>
#include <linux/etherdevice.h>

So it looks like this:

Code: 
#include <linux/netdevice.h>
#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,4,10)
#include <net/gso.h>
#endif
#include <linux/etherdevice.h>

Then you can try building the kernel module:
Code: 
dkms build -m r8168 -v 8.051.02 -k 6.5.11-4-pve

You can check if anything went wrong this way:
Code: 
cat /var/lib/dkms/r8168/8.051.02/build/make.log

You MIGHT need to install grub-efi-amd64 if you have related errors while building the module. If so, do this:

Code: 
apt install grub-efi-amd64

Then retry building the kernel module.

After that you should be able to upgrade the kernel to 6.5.11-4 and also upgrade Proxmox to 8.1:

Code: 
apt upgrade


ADDENDUM - What's wrong with the kernel module source code?

The skb_gso_segment C function definition was moved from the netdevice.h header file to net/gso.h in kernel 6.4.10 (if I'm not wrong) [1].

Hence the error when building the kernel module. The function definition couldn't be found.
The fix is just a matter of adding the net/gso.h header include.
However that's only necessary for kernel 6.4.10 forward. Hence the
Code: 
#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,4,10)
conditional statement and its matching
Code: 
$endif
statement around the include.

References:
[1] - https://lore.kernel.org/netfilter-devel/1367259744-8922-16-git-send-email-pablo@netfilter.org/
Click to expand...

Keep in mind r8169 is working on Kernel 6.5.11-4. I just tested.

So you can uninstall r8168-dkms completely and move on.
Just remember to remove r8169 from modprobe blacklist otherwise it will not be loaded at boot time.
 
  • Like
Reactions: Skad and shaunsul
For me I think is the nvidia card/module that is preventing me to upgrade:

Code: 
root@whitefractal:/etc/modprobe.d# apt dist-upgrade 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libnetfilter-acct1 libxnvctrl0 netdata-core netdata-plugins-bash netdata-plugins-python netdata-web proxmox-headers-6.2.16-10-pve proxmox-headers-6.2.16-12-pve proxmox-headers-6.2.16-14-pve proxmox-headers-6.2.16-15-pve
  proxmox-headers-6.2.16-18-pve proxmox-kernel-6.2.16-10-pve proxmox-kernel-6.2.16-12-pve proxmox-kernel-6.2.16-14-pve proxmox-kernel-6.2.16-8-pve
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
root@whitefractal:/etc/modprobe.d# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libnetfilter-acct1 libxnvctrl0 netdata-core netdata-plugins-bash netdata-plugins-python netdata-web proxmox-headers-6.2.16-10-pve proxmox-headers-6.2.16-12-pve proxmox-headers-6.2.16-14-pve proxmox-headers-6.2.16-15-pve
  proxmox-headers-6.2.16-18-pve proxmox-kernel-6.2.16-10-pve proxmox-kernel-6.2.16-12-pve proxmox-kernel-6.2.16-14-pve proxmox-kernel-6.2.16-8-pve
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y

Setting up proxmox-kernel-6.5.11-4-pve-signed (6.5.11-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.11-4-pve /boot/vmlinuz-6.5.11-4-pve
dkms: running auto installation service for kernel 6.5.11-4-pve.
Sign command: /lib/modules/6.5.11-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j20 modules KERNEL_UNAME=6.5.11-4-pve.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.11-4-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.11-4-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.11-4-pve-signed (--configure):
 installed proxmox-kernel-6.5.11-4-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.5:
 proxmox-kernel-6.5 depends on proxmox-kernel-6.5.11-4-pve-signed | proxmox-kernel-6.5.11-4-pve; however:
  Package proxmox-kernel-6.5.11-4-pve-signed is not configured yet.
  Package proxmox-kernel-6.5.11-4-pve is not installed.
  Package proxmox-kernel-6.5.11-4-pve-signed which provides proxmox-kernel-6.5.11-4-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.5; however:
  Package proxmox-kernel-6.5 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.5.11-4-pve-signed
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

I tried the suggestion here of renaming nvidia modules in /etc/modprobe.d from .conf to .conf_bak and restart the upgrade but it still doesn't..
any suggestions?
 
gonsa said:
For me I think is the nvidia card/module that is preventing me to upgrade:

Code: 
Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j20 modules KERNEL_UNAME=6.5.11-4-pve.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information.

I tried the suggestion here of renaming nvidia modules in /etc/modprobe.d from .conf to .conf_bak and restart the upgrade but it still doesn't..
any suggestions?
Click to expand...
Ask NVidia to provide you with a driver that works with this newer kernel. Send them /var/lib/dkms/nvidia-current/525.125.06/build/make.log for additional information. It's proprietary/closed source, so others cannot fix it for you.
 
gonsa said:
For me I think is the nvidia card/module that is preventing me to upgrade:

Code: 
root@whitefractal:/etc/modprobe.d# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libnetfilter-acct1 libxnvctrl0 netdata-core netdata-plugins-bash netdata-plugins-python netdata-web proxmox-headers-6.2.16-10-pve proxmox-headers-6.2.16-12-pve proxmox-headers-6.2.16-14-pve proxmox-headers-6.2.16-15-pve
  proxmox-headers-6.2.16-18-pve proxmox-kernel-6.2.16-10-pve proxmox-kernel-6.2.16-12-pve proxmox-kernel-6.2.16-14-pve proxmox-kernel-6.2.16-8-pve
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
root@whitefractal:/etc/modprobe.d# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libnetfilter-acct1 libxnvctrl0 netdata-core netdata-plugins-bash netdata-plugins-python netdata-web proxmox-headers-6.2.16-10-pve proxmox-headers-6.2.16-12-pve proxmox-headers-6.2.16-14-pve proxmox-headers-6.2.16-15-pve
  proxmox-headers-6.2.16-18-pve proxmox-kernel-6.2.16-10-pve proxmox-kernel-6.2.16-12-pve proxmox-kernel-6.2.16-14-pve proxmox-kernel-6.2.16-8-pve
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y

Setting up proxmox-kernel-6.5.11-4-pve-signed (6.5.11-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.11-4-pve /boot/vmlinuz-6.5.11-4-pve
dkms: running auto installation service for kernel 6.5.11-4-pve.
Sign command: /lib/modules/6.5.11-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j20 modules KERNEL_UNAME=6.5.11-4-pve.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.11-4-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.11-4-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.5.11-4-pve-signed (--configure):
 installed proxmox-kernel-6.5.11-4-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.5:
 proxmox-kernel-6.5 depends on proxmox-kernel-6.5.11-4-pve-signed | proxmox-kernel-6.5.11-4-pve; however:
  Package proxmox-kernel-6.5.11-4-pve-signed is not configured yet.
  Package proxmox-kernel-6.5.11-4-pve is not installed.
  Package proxmox-kernel-6.5.11-4-pve-signed which provides proxmox-kernel-6.5.11-4-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
 proxmox-default-kernel depends on proxmox-kernel-6.5; however:
  Package proxmox-kernel-6.5 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve:
 proxmox-ve depends on proxmox-default-kernel; however:
  Package proxmox-default-kernel is not configured yet.

dpkg: error processing package proxmox-ve (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 proxmox-kernel-6.5.11-4-pve-signed
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

I tried the suggestion here of renaming nvidia modules in /etc/modprobe.d from .conf to .conf_bak and restart the upgrade but it still doesn't..
any suggestions?
Click to expand...

Removing from modprobe is only changing IF a module gets loaded or not.
But you have dkms package installed to provide a kernel module. Updating the kernel will try to compile these packages so these would continue to work. Some will work (usually you'd require the kernel headers in order to compile these), but some simply are not compatible with newer versions of kernel (like the nvidia's).
 
After update I get the bellow message and it freezes.
1700850171474.png


Dell T430 - E-2288G - H730P
Reverting back to 6.2 works.
 
As far as I can see all looks fine with my Asrock J3710-ITX, Supermicro X10SLL-F and Supermicro X10SRM-F. No problems so far with GT710 passthrough, SAS2008 passthrough, Connectx-3, Intel i350-T4 and full system encryption via ZFS.
 
Last edited:
I've run into an odd breaking issue with SPICE audio.

If I add an ich9-intel-hda using the SPICE backend driver to a VM, that VM will fail to start with QEMU Exit Code 1 in the GUI log.

I had to try to start it via the CLI to see that the audio driver was the issue.
I'm reinstalling a VM now (I thought it was corrupted and deleted it), but after that's done I'll try to recreate the error and report the exact output back.

EDIT - Here's the error:
Code: 
# qm start 10999
audio: Could not init `spice' audio driver
start failed: QEMU exited with code 1
 
Last edited:
gonsa said:
525.125.06
Click to expand...

If this is the version (525.125.06-1~deb12u1) from the current Debian Bookworm repository: [1], it is expected, since the compatibility to the 6.5 kernel was only introduced in version: 525.125.06-2:
Code: 
nvidia-graphics-drivers (525.125.06-2) unstable; urgency=medium

  * Backport get_user_pages and pin_user_pages changes from
    535.86.05 to fix kernel module build for Linux 6.5.

 -- Andreas Beckmann <...>  Thu, 17 Aug 2023 00:34:55 +0200
Click to expand...
https://metadata.ftp-master.debian....vidia-graphics-drivers_525.125.06-3_changelog
which currently made it only into Debian Testing/Trixie with version: 525.125.06-3:
https://packages.debian.org/trixie/nvidia-driver

[1] https://packages.debian.org/bookworm/nvidia-driver
 
I have a question based on reading the changelog for 8.1. Sorry if I'm missing something obvious. :)

[LXC] Show privileged status as a separate row in the guest status view in the GUI.

What is the "guest status view" in the GUI?
 
After 8.04 to 8.1 upgrade my ceph managers won't start anymore:
Code: 
Nov 25 05:35:02 quake systemd[1]: Started ceph-mgr@quake.service - Ceph cluster manager daemon.
Nov 25 05:35:02 quake ceph-mgr[166427]: terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
Nov 25 05:35:02 quake ceph-mgr[166427]:   what():  filesystem error: directory iterator cannot open directory: No such file or directory [/usr/lib/ceph/mgr]
Nov 25 05:35:02 quake ceph-mgr[166427]: *** Caught signal (Aborted) **
Nov 25 05:35:02 quake ceph-mgr[166427]:  in thread 7fc22c33c000 thread_name:ceph-mgr
Nov 25 05:35:02 quake ceph-mgr[166427]:  ceph version 17.2.7 (e303afc2e967a4705b40a7e5f76067c10eea0484) quincy (stable)
Nov 25 05:35:02 quake ceph-mgr[166427]:  1: /lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0) [0x7fc22b65afd0]
Nov 25 05:35:02 quake ceph-mgr[166427]:  2: /lib/x86_64-linux-gnu/libc.so.6(+0x8ad3c) [0x7fc22b6a9d3c]
Nov 25 05:35:02 quake ceph-mgr[166427]:  3: gsignal()
Nov 25 05:35:02 quake ceph-mgr[166427]:  4: abort()
Nov 25 05:35:02 quake ceph-mgr[166427]:  5: /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9d919) [0x7fc22b49d919]
Nov 25 05:35:02 quake ceph-mgr[166427]:  6: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a) [0x7fc22b4a8e1a]
Nov 25 05:35:02 quake ceph-mgr[166427]:  7: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85) [0x7fc22b4a8e85]
Nov 25 05:35:02 quake ceph-mgr[166427]:  8: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8) [0x7fc22b4a90d8]
Nov 25 05:35:02 quake ceph-mgr[166427]:  9: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa0f3b) [0x7fc22b4a0f3b]
Nov 25 05:35:02 quake ceph-mgr[166427]:  10: (PyModuleRegistry::probe_modules(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const+0x14c) [0x563bb23141dc]
Nov 25 05:35:02 quake ceph-mgr[166427]:  11: (PyModuleRegistry::init()+0x1b6) [0x563bb2314b76]
Nov 25 05:35:02 quake ceph-mgr[166427]:  12: (MgrStandby::init()+0x637) [0x563bb22ed327]
Nov 25 05:35:02 quake ceph-mgr[166427]:  13: main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  14: /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) [0x7fc22b6461ca]
Nov 25 05:35:02 quake ceph-mgr[166427]:  15: __libc_start_main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  16: _start()
Nov 25 05:35:02 quake ceph-mgr[166427]: 2023-11-25T05:35:02.669+0200 7fc22c33c000 -1 *** Caught signal (Aborted) **
Nov 25 05:35:02 quake ceph-mgr[166427]:  in thread 7fc22c33c000 thread_name:ceph-mgr
Nov 25 05:35:02 quake ceph-mgr[166427]:  ceph version 17.2.7 (e303afc2e967a4705b40a7e5f76067c10eea0484) quincy (stable)
Nov 25 05:35:02 quake ceph-mgr[166427]:  1: /lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0) [0x7fc22b65afd0]
Nov 25 05:35:02 quake ceph-mgr[166427]:  2: /lib/x86_64-linux-gnu/libc.so.6(+0x8ad3c) [0x7fc22b6a9d3c]
Nov 25 05:35:02 quake ceph-mgr[166427]:  3: gsignal()
Nov 25 05:35:02 quake ceph-mgr[166427]:  4: abort()
Nov 25 05:35:02 quake ceph-mgr[166427]:  5: /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9d919) [0x7fc22b49d919]
Nov 25 05:35:02 quake ceph-mgr[166427]:  6: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a) [0x7fc22b4a8e1a]
Nov 25 05:35:02 quake ceph-mgr[166427]:  7: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85) [0x7fc22b4a8e85]
Nov 25 05:35:02 quake ceph-mgr[166427]:  8: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8) [0x7fc22b4a90d8]
Nov 25 05:35:02 quake ceph-mgr[166427]:  9: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa0f3b) [0x7fc22b4a0f3b]
Nov 25 05:35:02 quake ceph-mgr[166427]:  10: (PyModuleRegistry::probe_modules(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const+0x14c) [0x563bb23141dc]
Nov 25 05:35:02 quake ceph-mgr[166427]:  11: (PyModuleRegistry::init()+0x1b6) [0x563bb2314b76]
Nov 25 05:35:02 quake ceph-mgr[166427]:  12: (MgrStandby::init()+0x637) [0x563bb22ed327]
Nov 25 05:35:02 quake ceph-mgr[166427]:  13: main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  14: /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) [0x7fc22b6461ca]
Nov 25 05:35:02 quake ceph-mgr[166427]:  15: __libc_start_main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  16: _start()
Nov 25 05:35:02 quake ceph-mgr[166427]:  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
Nov 25 05:35:02 quake ceph-mgr[166427]:      0> 2023-11-25T05:35:02.669+0200 7fc22c33c000 -1 *** Caught signal (Aborted) **
Nov 25 05:35:02 quake ceph-mgr[166427]:  in thread 7fc22c33c000 thread_name:ceph-mgr
Nov 25 05:35:02 quake ceph-mgr[166427]:  ceph version 17.2.7 (e303afc2e967a4705b40a7e5f76067c10eea0484) quincy (stable)
Nov 25 05:35:02 quake ceph-mgr[166427]:  1: /lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0) [0x7fc22b65afd0]
Nov 25 05:35:02 quake ceph-mgr[166427]:  2: /lib/x86_64-linux-gnu/libc.so.6(+0x8ad3c) [0x7fc22b6a9d3c]
Nov 25 05:35:02 quake ceph-mgr[166427]:  3: gsignal()
Nov 25 05:35:02 quake ceph-mgr[166427]:  4: abort()
Nov 25 05:35:02 quake ceph-mgr[166427]:  5: /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9d919) [0x7fc22b49d919]
Nov 25 05:35:02 quake ceph-mgr[166427]:  6: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a) [0x7fc22b4a8e1a]
Nov 25 05:35:02 quake ceph-mgr[166427]:  7: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85) [0x7fc22b4a8e85]
Nov 25 05:35:02 quake ceph-mgr[166427]:  8: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8) [0x7fc22b4a90d8]
Nov 25 05:35:02 quake ceph-mgr[166427]:  9: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa0f3b) [0x7fc22b4a0f3b]
Nov 25 05:35:02 quake ceph-mgr[166427]:  10: (PyModuleRegistry::probe_modules(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const+0x14c) [0x563bb23141dc]
Nov 25 05:35:02 quake ceph-mgr[166427]:  11: (PyModuleRegistry::init()+0x1b6) [0x563bb2314b76]
Nov 25 05:35:02 quake ceph-mgr[166427]:  12: (MgrStandby::init()+0x637) [0x563bb22ed327]
Nov 25 05:35:02 quake ceph-mgr[166427]:  13: main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  14: /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) [0x7fc22b6461ca]
Nov 25 05:35:02 quake ceph-mgr[166427]:  15: __libc_start_main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  16: _start()
Nov 25 05:35:02 quake ceph-mgr[166427]:  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
Nov 25 05:35:02 quake ceph-mgr[166427]:      0> 2023-11-25T05:35:02.669+0200 7fc22c33c000 -1 *** Caught signal (Aborted) **
Nov 25 05:35:02 quake ceph-mgr[166427]:  in thread 7fc22c33c000 thread_name:ceph-mgr
Nov 25 05:35:02 quake ceph-mgr[166427]:  ceph version 17.2.7 (e303afc2e967a4705b40a7e5f76067c10eea0484) quincy (stable)
Nov 25 05:35:02 quake ceph-mgr[166427]:  1: /lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0) [0x7fc22b65afd0]
Nov 25 05:35:02 quake ceph-mgr[166427]:  2: /lib/x86_64-linux-gnu/libc.so.6(+0x8ad3c) [0x7fc22b6a9d3c]
Nov 25 05:35:02 quake ceph-mgr[166427]:  3: gsignal()
Nov 25 05:35:02 quake ceph-mgr[166427]:  4: abort()
Nov 25 05:35:02 quake ceph-mgr[166427]:  5: /lib/x86_64-linux-gnu/libstdc++.so.6(+0x9d919) [0x7fc22b49d919]
Nov 25 05:35:02 quake ceph-mgr[166427]:  6: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a) [0x7fc22b4a8e1a]
Nov 25 05:35:02 quake ceph-mgr[166427]:  7: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85) [0x7fc22b4a8e85]
Nov 25 05:35:02 quake ceph-mgr[166427]:  8: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8) [0x7fc22b4a90d8]
Nov 25 05:35:02 quake ceph-mgr[166427]:  9: /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa0f3b) [0x7fc22b4a0f3b]
Nov 25 05:35:02 quake ceph-mgr[166427]:  10: (PyModuleRegistry::probe_modules(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const+0x14c) [0x563bb23141dc]
Nov 25 05:35:02 quake ceph-mgr[166427]:  11: (PyModuleRegistry::init()+0x1b6) [0x563bb2314b76]
Nov 25 05:35:02 quake ceph-mgr[166427]:  12: (MgrStandby::init()+0x637) [0x563bb22ed327]
Nov 25 05:35:02 quake ceph-mgr[166427]:  13: main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  14: /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) [0x7fc22b6461ca]
Nov 25 05:35:02 quake ceph-mgr[166427]:  15: __libc_start_main()
Nov 25 05:35:02 quake ceph-mgr[166427]:  16: _start()
Nov 25 05:35:02 quake ceph-mgr[166427]:  NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.
Nov 25 05:35:02 quake systemd[1]: ceph-mgr@quake.service: Main process exited, code=killed, status=6/ABRT
Nov 25 05:35:02 quake systemd[1]: ceph-mgr@quake.service: Failed with result 'signal'.
Nov 25 05:35:12 quake systemd[1]: ceph-mgr@quake.service: Scheduled restart job, restart counter is at 3.
Nov 25 05:35:12 quake systemd[1]: Stopped ceph-mgr@quake.service - Ceph cluster manager daemon.
Nov 25 05:35:12 quake systemd[1]: ceph-mgr@quake.service: Start request repeated too quickly.
Nov 25 05:35:12 quake systemd[1]: ceph-mgr@quake.service: Failed with result 'signal'.
Nov 25 05:35:12 quake systemd[1]: Failed to start ceph-mgr@quake.service - Ceph cluster manager daemon.

I had 2 managers. Tried to add third one on 3rd node, and it bailed out the same way.

Running: ceph version 17.2.7 (e303afc2e967a4705b40a7e5f76067c10eea0484) quincy (stable)
 
Last edited:
Well , initially it seemed fix to get managers running was to:
Bash: 
mkdir /usr/lib/ceph/mgr

But now it complains that modules are not available:
Code: 
HEALTH_ERR: 10 mgr modules have failed
Module 'balancer' has failed: Not found or unloadable
Module 'crash' has failed: Not found or unloadable
Module 'devicehealth' has failed: Not found or unloadable
Module 'orchestrator' has failed: Not found or unloadable
Module 'pg_autoscaler' has failed: Not found or unloadable
Module 'progress' has failed: Not found or unloadable
Module 'rbd_support' has failed: Not found or unloadable
Module 'status' has failed: Not found or unloadable
Module 'telemetry' has failed: Not found or unloadable
Module 'volumes' has failed: Not found or unloadable

Before creating this dir I also upgraded to v18 (ceph version 18.2.0 (d724bab467c1c4e2a89e8070f01037ae589a37ca) reef (stable))

So I noticed that modules seem to reside in /usr/share/ceph/mgr. So changed the ceph.conf to reflect that. It shows healthy now, but will complain about every module in the syslog:
Code: 
Nov 25 06:20:03 phoenix ceph-mgr[204812]: 2023-11-25T06:20:03.224+0200 7f45cd688280 -1 mgr[py] Module snap_schedule has missing NOTIFY_TYPES member
Nov 25 06:20:03 phoenix ceph-mgr[204812]: 2023-11-25T06:20:03.380+0200 7f45cd688280 -1 mgr[py] Module rbd_support has missing NOTIFY_TYPES member
Nov 25 06:20:03 phoenix ceph-mgr[204812]: 2023-11-25T06:20:03.508+0200 7f45cd688280 -1 mgr[py] Module osd_perf_query has missing NOTIFY_TYPES member
Nov 25 06:20:03 phoenix ceph-mgr[204812]: 2023-11-25T06:20:03.860+0200 7f45cd688280 -1 mgr[py] Module nfs has missing NOTIFY_TYPES member
Nov 25 06:20:03 phoenix ceph-mgr[204812]: 2023-11-25T06:20:03.956+0200 7f45cd688280 -1 mgr[py] Module zabbix has missing NOTIFY_TYPES member
Nov 25 06:20:04 phoenix ceph-mgr[204812]: 2023-11-25T06:20:04.312+0200 7f45cd688280 -1 mgr[py] Module prometheus has missing NOTIFY_TYPES member
Nov 25 06:20:04 phoenix ceph-mgr[204812]: 2023-11-25T06:20:04.508+0200 7f45cd688280 -1 mgr[py] Module devicehealth has missing NOTIFY_TYPES member
Nov 25 06:20:04 phoenix ceph-mgr[204812]: 2023-11-25T06:20:04.608+0200 7f45cd688280 -1 mgr[py] Module influx has missing NOTIFY_TYPES member
Nov 25 06:20:04 phoenix ceph-mgr[204812]: 2023-11-25T06:20:04.696+0200 7f45cd688280 -1 mgr[py] Module osd_support has missing NOTIFY_TYPES member
Nov 25 06:20:04 phoenix ceph-mgr[204812]: 2023-11-25T06:20:04.824+0200 7f45cd688280 -1 mgr[py] Module crash has missing NOTIFY_TYPES member
Nov 25 06:20:04 phoenix ceph-mgr[204812]: 2023-11-25T06:20:04.932+0200 7f45cd688280 -1 mgr[py] Module balancer has missing NOTIFY_TYPES member
Nov 25 06:20:05 phoenix ceph-mgr[204812]: 2023-11-25T06:20:05.184+0200 7f45cd688280 -1 mgr[py] Module telemetry has missing NOTIFY_TYPES member
Nov 25 06:20:05 phoenix ceph-mgr[204812]: 2023-11-25T06:20:05.400+0200 7f45cd688280 -1 mgr[py] Module test_orchestrator has missing NOTIFY_TYPES member
Nov 25 06:20:05 phoenix ceph-mgr[204812]: 2023-11-25T06:20:05.528+0200 7f45cd688280 -1 mgr[py] Module pg_autoscaler has missing NOTIFY_TYPES member
Nov 25 06:20:05 phoenix ceph-mgr[204812]: 2023-11-25T06:20:05.624+0200 7f45cd688280 -1 mgr[py] Module selftest has missing NOTIFY_TYPES member
Nov 25 06:20:05 phoenix ceph-mgr[204812]: 2023-11-25T06:20:05.724+0200 7f45cd688280 -1 mgr[py] Module progress has missing NOTIFY_TYPES member
Nov 25 06:20:05 phoenix ceph-mgr[204812]: 2023-11-25T06:20:05.820+0200 7f45cd688280 -1 mgr[py] Module telegraf has missing NOTIFY_TYPES member
Nov 25 06:20:06 phoenix ceph-mgr[204812]: 2023-11-25T06:20:06.028+0200 7f45cd688280 -1 mgr[py] Module orchestrator has missing NOTIFY_TYPES member
Nov 25 06:20:06 phoenix ceph-mgr[204812]: 2023-11-25T06:20:06.464+0200 7f45cd688280 -1 mgr[py] Module volumes has missing NOTIFY_TYPES member
Nov 25 06:20:06 phoenix ceph-mgr[204812]: 2023-11-25T06:20:06.572+0200 7f45cd688280 -1 mgr[py] Module alerts has missing NOTIFY_TYPES member
Nov 25 06:20:06 phoenix ceph-mgr[204812]: 2023-11-25T06:20:06.696+0200 7f45cd688280 -1 mgr[py] Module status has missing NOTIFY_TYPES member
Nov 25 06:20:07 phoenix ceph-mgr[204812]: 2023-11-25T06:20:07.360+0200 7f45cd688280 -1 mgr[py] Module iostat has missing NOTIFY_TYPES member
 
Last edited:
Hello Experts,

I believe I did install a nvidia patch and that this breaks the upgrade. Which package should I remove for this to work? nvidia-tesla-470-470.199.02 ?

Code: 
root@BareBone:~# apt dist-upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait    
Calcul de la mise à jour... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
4 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] O
Paramétrage de proxmox-kernel-6.5.11-4-pve-signed (6.5.11-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.11-4-pve /boot/vmlinuz-6.5.11-4-pve
dkms: running auto installation service for kernel 6.5.11-4-pve.
Sign command: /lib/modules/6.5.11-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
applying patch cc_version_check-gcc5.patch...patching file conftest.sh

applying patch bashisms.patch...patching file conftest.sh

applying patch linux-2.6.34-dev_pm_info-runtime_auto.patch...patching file conftest.sh

applying patch 0010-backport-pci-dma-changes-for-ppc64el.patch...patching file nvidia/nv.c

applying patch ppc64el.patch...patching file nvidia/nvlink_common.h

applying patch fragile-ARCH.patch...patching file Makefile

applying patch use-kbuild-compiler.patch...patching file Makefile
patching file Kbuild

applying patch use-kbuild-flags.patch...patching file Kbuild
patching file nvidia/nvidia.Kbuild
patching file Makefile
patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch conftest-verbose.patch...patching file Kbuild

applying patch conftest-prefer-arch-headers.patch...patching file conftest.sh


Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.5.11-4-pve.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.199.02/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.11-4-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.11-4-pve-signed.postinst line 20.
dpkg: erreur de traitement du paquet proxmox-kernel-6.5.11-4-pve-signed (--configure) :
 le sous-processus paquet proxmox-kernel-6.5.11-4-pve-signed script post-installation installé a renvoyé un état de sortie d'erreur 2
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-kernel-6.5 :
 proxmox-kernel-6.5 dépend de proxmox-kernel-6.5.11-4-pve-signed | proxmox-kernel-6.5.11-4-pve; cependant :
 Le paquet proxmox-kernel-6.5.11-4-pve-signed n'est pas encore configuré.
  Le paquet proxmox-kernel-6.5.11-4-pve n'est pas installé.
  Le paquet proxmox-kernel-6.5.11-4-pve-signed qui fournit proxmox-kernel-6.5.11-4-pve n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-kernel-6.5 (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-default-kernel :
 proxmox-default-kernel dépend de proxmox-kernel-6.5; cependant :
 Le paquet proxmox-kernel-6.5 n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-default-kernel (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-ve :
 proxmox-ve dépend de proxmox-default-kernel; cependant :
 Le paquet proxmox-default-kernel n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-ve (--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 proxmox-kernel-6.5.11-4-pve-signed
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)

Of course many thanks !!! and good WE too
 
Last edited:
Hi, I have a problem with kernel version 6.5.11-4-after migration VMs freeze. I reverted back to version 6.2.16-19-pve but the problem with that version is that VMs sometimes freeze on Init RAM when I boot.

How do I fix the problem please?
 
8.0 to 8.1:
TASK ERROR: EFI base image '/usr/share/pve-edk2-firmware//AAVMF_CODE.fd' not found
 
no luck trying to remove the package

Code: 
root@BareBone:~# apt remove nvidia-tesla-470-driver
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait     
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
  libegl-nvidia-tesla-470-0 libgles-nvidia-tesla-470-1 libgles-nvidia-tesla-470-2 libgles1 libnvidia-egl-wayland1 libnvidia-tesla-470-encode1 libnvidia-tesla-470-nvcuvid1 nvidia-egl-common nvidia-tesla-470-driver-bin
  nvidia-tesla-470-driver-libs nvidia-tesla-470-egl-icd
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
  nvidia-tesla-470-driver
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
4 partiellement installés ou enlevés.
Après cette opération, 1 322 ko d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] O
(Lecture de la base de données... 241072 fichiers et répertoires déjà installés.)
Suppression de nvidia-tesla-470-driver (470.199.02-1~deb12u1) ...
Paramétrage de proxmox-kernel-6.5.11-4-pve-signed (6.5.11-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.11-4-pve /boot/vmlinuz-6.5.11-4-pve
dkms: running auto installation service for kernel 6.5.11-4-pve.
Sign command: /lib/modules/6.5.11-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
applying patch cc_version_check-gcc5.patch...patching file conftest.sh

applying patch bashisms.patch...patching file conftest.sh

applying patch linux-2.6.34-dev_pm_info-runtime_auto.patch...patching file conftest.sh

applying patch 0010-backport-pci-dma-changes-for-ppc64el.patch...patching file nvidia/nv.c

applying patch ppc64el.patch...patching file nvidia/nvlink_common.h

applying patch fragile-ARCH.patch...patching file Makefile

applying patch use-kbuild-compiler.patch...patching file Makefile
patching file Kbuild

applying patch use-kbuild-flags.patch...patching file Kbuild
patching file nvidia/nvidia.Kbuild
patching file Makefile
patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch conftest-verbose.patch...patching file Kbuild

applying patch conftest-prefer-arch-headers.patch...patching file conftest.sh


Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.5.11-4-pve......(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.199.02/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.11-4-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.11-4-pve-signed.postinst line 20.
dpkg: erreur de traitement du paquet proxmox-kernel-6.5.11-4-pve-signed (--configure) :
 le sous-processus paquet proxmox-kernel-6.5.11-4-pve-signed script post-installation installé a renvoyé un état de sortie d'erreur 2
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-kernel-6.5 :
 proxmox-kernel-6.5 dépend de proxmox-kernel-6.5.11-4-pve-signed | proxmox-kernel-6.5.11-4-pve; cependant :
 Le paquet proxmox-kernel-6.5.11-4-pve-signed n'est pas encore configuré.
  Le paquet proxmox-kernel-6.5.11-4-pve n'est pas installé.
  Le paquet proxmox-kernel-6.5.11-4-pve-signed qui fournit proxmox-kernel-6.5.11-4-pve n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-kernel-6.5 (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-default-kernel :
 proxmox-default-kernel dépend de proxmox-kernel-6.5; cependant :
 Le paquet proxmox-kernel-6.5 n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-default-kernel (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-ve :
 proxmox-ve dépend de proxmox-default-kernel; cependant :
 Le paquet proxmox-default-kernel n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-ve (--configure) :
 problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
 proxmox-kernel-6.5.11-4-pve-signed
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@BareBone:~# apt autoclean && sudo apt autoremove
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait     
Del libldb2 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 [161 kB]
Del gir1.2-javascriptcoregtk-4.0 2.42.1-1~deb12u1 [46,8 kB]
Del samba-common 2:4.17.10+dfsg-0+deb12u1 [85,4 kB]
Del firefox-esr 115.3.0esr-1~deb12u1 [63,1 MB]
Del firefox-esr 102.14.0esr-1~deb12u1 [59,4 MB]
Del libjavascriptcoregtk-4.0-18 2.42.1-1~deb12u1 [7 529 kB]
Del samba-dsdb-modules 2:4.17.10+dfsg-0+deb12u1 [315 kB]
Del gir1.2-webkit2-4.0 2.42.1-1~deb12u1 [102 kB]
Del firefox-esr 102.15.0esr-1~deb12u1 [59,5 MB]
Del libsmbclient 2:4.17.10+dfsg-0+deb12u1 [81,5 kB]
Del libwebkit2gtk-4.0-37 2.42.1-1~deb12u1 [20,3 MB]
Del samba-libs 2:4.17.10+dfsg-0+deb12u1 [5 660 kB]
Del libedgetpu1-std 16.0 [387 kB]
Del python3-ldb 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 [59,5 kB]
Del samba 2:4.17.10+dfsg-0+deb12u1 [944 kB]
Del firefox-esr 115.4.0esr-1~deb12u1 [63,1 MB]
Del samba-common-bin 2:4.17.10+dfsg-0+deb12u1 [1 181 kB]
Del libwbclient0 2:4.17.10+dfsg-0+deb12u1 [52,7 kB]
Del python3-samba 2:4.17.10+dfsg-0+deb12u1 [2 821 kB]
Del smbclient 2:4.17.10+dfsg-0+deb12u1 [442 kB]
Del samba-vfs-modules 2:4.17.10+dfsg-0+deb12u1 [427 kB]
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait     
Les paquets suivants seront ENLEVÉS :
  libegl-nvidia-tesla-470-0 libgles-nvidia-tesla-470-1 libgles-nvidia-tesla-470-2 libgles1 libnvidia-egl-wayland1 libnvidia-tesla-470-encode1 libnvidia-tesla-470-nvcuvid1 nvidia-egl-common nvidia-tesla-470-driver-bin
  nvidia-tesla-470-driver-libs nvidia-tesla-470-egl-icd
0 mis à jour, 0 nouvellement installés, 11 à enlever et 0 non mis à jour.
4 partiellement installés ou enlevés.
Après cette opération, 9 011 ko d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] O
(Lecture de la base de données... 241002 fichiers et répertoires déjà installés.)
Suppression de nvidia-tesla-470-driver-libs:amd64 (470.199.02-1~deb12u1) ...
Suppression de nvidia-tesla-470-egl-icd:amd64 (470.199.02-1~deb12u1) ...
Suppression de libegl-nvidia-tesla-470-0:amd64 (470.199.02-1~deb12u1) ...
Suppression de libgles-nvidia-tesla-470-1:amd64 (470.199.02-1~deb12u1) ...
Suppression de libgles-nvidia-tesla-470-2:amd64 (470.199.02-1~deb12u1) ...
Suppression de libgles1:amd64 (1.6.0-1) ...
Suppression de libnvidia-egl-wayland1:amd64 (1:1.1.10-1) ...
Suppression de libnvidia-tesla-470-encode1:amd64 (470.199.02-1~deb12u1) ...
Suppression de libnvidia-tesla-470-nvcuvid1:amd64 (470.199.02-1~deb12u1) ...
Suppression de nvidia-egl-common (525.125.06-1~deb12u1) ...
Suppression de nvidia-tesla-470-driver-bin (470.199.02-1~deb12u1) ...
Paramétrage de proxmox-kernel-6.5.11-4-pve-signed (6.5.11-4) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.5.11-4-pve /boot/vmlinuz-6.5.11-4-pve
dkms: running auto installation service for kernel 6.5.11-4-pve.
Sign command: /lib/modules/6.5.11-4-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
applying patch cc_version_check-gcc5.patch...patching file conftest.sh

applying patch bashisms.patch...patching file conftest.sh

applying patch linux-2.6.34-dev_pm_info-runtime_auto.patch...patching file conftest.sh

applying patch 0010-backport-pci-dma-changes-for-ppc64el.patch...patching file nvidia/nv.c

applying patch ppc64el.patch...patching file nvidia/nvlink_common.h

applying patch fragile-ARCH.patch...patching file Makefile

applying patch use-kbuild-compiler.patch...patching file Makefile
patching file Kbuild

applying patch use-kbuild-flags.patch...patching file Kbuild
patching file nvidia/nvidia.Kbuild
patching file Makefile
patching file nvidia-modeset/nvidia-modeset.Kbuild

applying patch conftest-verbose.patch...patching file Kbuild

applying patch conftest-prefer-arch-headers.patch...patching file conftest.sh


Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.5.11-4-pve.....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.11-4-pve (x86_64)
Consult /var/lib/dkms/nvidia-tesla-470/470.199.02/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.5.11-4-pve failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.5.11-4-pve-signed.postinst line 20.
dpkg: erreur de traitement du paquet proxmox-kernel-6.5.11-4-pve-signed (--configure) :
 le sous-processus paquet proxmox-kernel-6.5.11-4-pve-signed script post-installation installé a renvoyé un état de sortie d'erreur 2
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-kernel-6.5 :
 proxmox-kernel-6.5 dépend de proxmox-kernel-6.5.11-4-pve-signed | proxmox-kernel-6.5.11-4-pve; cependant :
 Le paquet proxmox-kernel-6.5.11-4-pve-signed n'est pas encore configuré.
  Le paquet proxmox-kernel-6.5.11-4-pve n'est pas installé.
  Le paquet proxmox-kernel-6.5.11-4-pve-signed qui fournit proxmox-kernel-6.5.11-4-pve n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-kernel-6.5 (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-default-kernel :
 proxmox-default-kernel dépend de proxmox-kernel-6.5; cependant :
 Le paquet proxmox-kernel-6.5 n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-default-kernel (--configure) :
 problèmes de dépendances - laissé non configuré
dpkg: des problèmes de dépendances empêchent la configuration de proxmox-ve :
 proxmox-ve dépend de proxmox-default-kernel; cependant :
 Le paquet proxmox-default-kernel n'est pas encore configuré.

dpkg: erreur de traitement du paquet proxmox-ve (--configure) :
 problèmes de dépendances - laissé non configuré
Traitement des actions différées (« triggers ») pour libc-bin (2.36-9+deb12u3) ...
Traitement des actions différées (« triggers ») pour glx-alternative-mesa (1.2.2) ...
update-alternatives: avertissement: forçage de la réinstallation de l'alternative /usr/lib/nvidia car le groupe de liens glx est cassé
update-alternatives: avertissement: création de /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1 abandonnée car le fichier associé /usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1 (du groupe de liens glx) n'existe pas
update-alternatives: avertissement: création de /usr/bin/nvidia-bug-report.sh abandonnée car le fichier associé /usr/lib/nvidia/nvidia-bug-report.sh (du groupe de liens glx) n'existe pas
Traitement des actions différées (« triggers ») pour nvidia-tesla-470-alternative (470.199.02-1~deb12u1) ...
update-alternatives: avertissement: forçage de la réinstallation de l'alternative /usr/lib/nvidia/tesla-470 car le groupe de liens nvidia est cassé
Traitement des actions différées (« triggers ») pour libc-bin (2.36-9+deb12u3) ...
Traitement des actions différées (« triggers ») pour glx-alternative-nvidia (1.2.2) ...
Traitement des actions différées (« triggers ») pour glx-alternative-mesa (1.2.2) ...
Traitement des actions différées (« triggers ») pour update-glx (1.2.2) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.36-9+deb12u3) ...
Traitement des actions différées (« triggers ») pour glx-alternative-nvidia (1.2.2) ...
Traitement des actions différées (« triggers ») pour libc-bin (2.36-9+deb12u3) ...
Traitement des actions différées (« triggers ») pour initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-19-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.
System booted in EFI-mode but 'grub-efi-amd64' meta-package not installed!
Install 'grub-efi-amd64' to get updates.
Des erreurs ont été rencontrées pendant l'exécution :
 proxmox-kernel-6.5.11-4-pve-signed
 proxmox-kernel-6.5
 proxmox-default-kernel
 proxmox-ve
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
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