If it is possible to run -12, why did you switch back to -11 ?I change grub config file and set kernel 2.6.32-11 as default and wait for next release. It's possible to reinstall kernel 2.6.32-12 - was removed during the update.
If it is possible to run -12, why did you switch back to -11 ?I change grub config file and set kernel 2.6.32-11 as default and wait for next release. It's possible to reinstall kernel 2.6.32-12 - was removed during the update.
Btw, really a kernel upgrade should never ever remove previous version.
proxmox:~# LANG=C aptitude -d full-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be installed:
pve-kernel-2.6.32-7-pve{a}
The following packages will be REMOVED:
pve-kernel-2.6.32-6-pve{u}
The following packages will be upgraded:
apache2 apache2-mpm-prefork apache2-utils apache2.2-common base-files libapr1 libpq5 libssl0.9.8 libxml2 openssl proxmox-ve-2.6.32 pve-firmware
The following packages are RECOMMENDED but will NOT be installed:
xml-core
12 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B/48.8MB of archives. After unpacking 16.4kB will be freed.
Do you want to continue? [Y/n/?] ^C
proxmox:~#
proxmox:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.32-6-pve: 2.6.32-55
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
We use essential cookies to make this site work, and optional cookies to enhance your experience.