New Proxmox VE Kernel (2.6.24-9)

tom

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
15,914
1,181
273
Hi all,

We just moved the latest kernel (pve-kernel-2.6.24-9-pve_2.6.24-18_amd64.deb) from the testing to the stable repository (pve).

Release notes:

  • update kvm to kvm-kmod-2.6.31.6.tar.bz2
  • update e1000e to e1000e-1.0.15.tar.gz
  • kernel security fixes
In order to use this kernel:

Code: 
apt-get update
apt-get dist-upgrade
and reboot!
 
Last edited by a moderator:
tom said:
Hi all,

We just moved the latest kernel (pve-kernel-2.6.24-9-pve_2.6.24-18_amd64.deb) from the testing to the stable repository (pve).

Release notes:

  • update kvm to kvm-kmod-2.6.31.6.tar.bz2
  • update e1000e to e1000e-1.0.15.tar.gz
  • kernel security fixes
In order to use this kernel:

Code: 
apt-get update
apt-get dist-upgrade
and reboot!
Click to expand...

I recomend all use aptcron to inform about updates automatic by mail.
Not see any comments at changelog. (see above)

This upgrade affects openvz? will be stop work or not?

Thanks.

----------------------------------------------------------------The following packages are currently pending an upgrade:

pve-kernel 2.6.24-18
pve-kernel-2.6.24-9-pve 2.6.24-18

========================================================================

Package Details:

Reading changelogs...
========================================================================

You can perform the upgrade by issuing the command:

aptitude full-upgrade
 
no changes to OpenVZ, as written in the release notes.
 
Just installed this Kernel and the Machine does not come up again.
I can boot into an older Kernel without pve.

Can you please give me a hint where to start troubleshooting?

Thanks
Matthias
 
Mhue said:
Just installed this Kernel and the Machine does not come up again.
I can boot into an older Kernel without pve.

Can you please give me a hint where to start troubleshooting?

Thanks
Matthias
Click to expand...

I assume the server was not a standard ISO install? (as there is an older kernel without pve on it)

So you need to provide all info.
 
Yes, i was not able to install the iso. I installed it on a plain debian lenny installation. So far it worked like a charm.
I´m on an Hetzner EQ4 and rebooted the machine into vkvm to get access. The console shows me " switch to root: can´t open /dev/console : no such file or directory
Kernel Panic, not syncing: Attemt to kill init!

Well i installed this weeks ago and unfortunately i´ve been to lazy to write down what i did to get it run. I only remeber that i had to change in a configfile an eth1 entry to eth0 to get it accessable via network.
But now it seems that the machine does not even start.

Cause of the Kernel-Panic the syslog does not come up early enough so i see no entrys there which would help.

the "working" Kernel is 2.6.26-2

What info´s do you need to help me?

Sorry for my weak English

Thanks so far
Matthias
 
Sorry for this too fast shout for help.
I did an update-initramfs -k 2.6.24-9-pve -v -u -t
and now the machine is up and running again.
This time this will run into my worklog.

Well i´m not so experienced into all this pve-stuff. But why
do i always have to manually create the initramfs image to get my
System running?
Shouldn´t this be done by aptitude?

Anyway, thanks for you fast answer

Matthias
 
Mhue said:
Sorry for this too fast shout for help.
I did an update-initramfs -k 2.6.24-9-pve -v -u -t
and now the machine is up and running again.
This time this will run into my worklog.

Well i´m not so experienced into all this pve-stuff. But why
do i always have to manually create the initramfs image to get my
System running?
Shouldn´t this be done by aptitude?

Anyway, thanks for you fast answer

Matthias
Click to expand...

for standard system you do not need anything special. do you run unsupported software raid?
 
The Standard-Image from Hetzner comes with Sofware-Raid configuration. I disabled this before installing. But anyway after the installation mdadm is started but i don´t have any raid configured.

Would it help do disable mdadm at boot to prevent the server not starting next time afer updating the Kernel?
 
i have the server in rescue mode i can give access to you so you can check. let me know for send you a email whit the login info.
 
if you want no fix anything only see why after upgrade this happen this go to happen to allot people, this is no a issue i create is a issue from upgrade.
 
Again, I will not login to your server - I will only do that if you have a valid support ticket.

If you want free support, provide all relevant info using this forum. For example, post a screenshot of the boot screen showing the error message.
 
You must log in or register to reply here.
Top Bottom